Re: Cannot clone from anonymous git

On 13 May 2016 15:42, Eduardo A. Bustamante López wrote: > http://savannah.gnu.org/git/?group=bash lists: > > | Getting a Copy of the Git Repository > | > | Anonymous clone: > | > | git clone git://git.savannah.gnu.org/bash.git > | > | Member clone: > | > | git clone @git.sv.gnu.org:/

Re: declare [-+]n behavior on existing (chained) namerefs

On Thu, May 5, 2016 at 2:22 PM, Chet Ramey wrote: > The only buggy behavior when inside of functions (ignoring scope issues) > > seems to be that `declare -n ref’ unsets the value of $ref if it > previously > > pointed to a variable that is unset. > > I fixed this as part of making other changes

Cannot clone from anonymous git

http://savannah.gnu.org/git/?group=bash lists: | Getting a Copy of the Git Repository | | Anonymous clone: | | git clone git://git.savannah.gnu.org/bash.git | | Member clone: | | git clone @git.sv.gnu.org:/srv/git/bash.git When I try to clone: | dualbus@hp ~ % git clone git://git.s

avoid mktemp/mkstemp internally

i was pointed at a bug report for FreeBSD systems [1] where running lots of processes in parallel would randomly fail with errors like: cannot make pipe for process substitution: File exists upstream FreeBSD addressed this by defining USE_MKTEMP [2] & USE_MKSTEMP [3] when building bash. looking

Re: nameref in temp environment

hi, there are two issues here, small regressions. I think in tmpenv we should create the variable unconditionally (concerning the namerefs), and should not follow the namerefs on checking if the variable exists: diff --git a/variables.c b/variables.c index 1877b17..f149b66 100644 --- a/variab