about summary refs log tree commit diff
path: root/git (follow)
Commit message (Expand)AuthorAge
* Use GIT-1.7.4Lars Hjemli2011-02-19
* Use GIT-1.7.3Lars Hjemli2010-09-19
* Use GIT-1.7.2.2Lars Hjemli2010-08-22
* Use GIT-1.7.0Lars Hjemli2010-02-27
* Use GIT-1.6.4.3Lars Hjemli2009-09-13
* Use GIT-1.6.3.4Lars Hjemli2009-08-16
* Use GIT-1.6.1.1Lars Hjemli2009-02-01
* Use GIT-1.6.1Lars Hjemli2008-12-26
* Use GIT-1.6.0.3Lars Hjemli2008-11-06
* Use GIT-1.6.0.2Lars Hjemli2008-10-05
* Use GIT-1.6.0.1Lars Hjemli2008-09-02
* Use GIT-1.6.0Lars Hjemli2008-09-01
* Use GIT-1.6.0.rc1Lars Hjemli2008-08-06
* Use GIT-1.6.0-rc0Lars Hjemli2008-07-21
* Use GIT-1.5.6Lars Hjemli2008-06-25
* Use GIT-1.5.5.1Lars Hjemli2008-05-18
* Use GIT-1.5.5Lars Hjemli2008-04-09
* Use GIT-1.5.5-rc2Lars Hjemli2008-04-01
* Use GIT-1.5.5.rc1Lars Hjemli2008-03-23
* Use GIT-1.5.4.4Lars Hjemli2008-03-17
* Use GIT-1.5.4.1Lars Hjemli2008-02-16
* Use GIT-1.5.4Lars Hjemli2008-02-02
* Use GIT-1.5.4.rc5Lars Hjemli2008-01-28
* Use GIT-1.5.4.rc4Lars Hjemli2008-01-21
* Use GIT-1.5.3.8Lars Hjemli2008-01-10
* Use GIT-1.5.3.5Lars Hjemli2007-11-03
* Use git-1.5.3.3Lars Hjemli2007-10-01
* Upgrade to GIT 1.5.3.2Lars Hjemli2007-09-20
* cgit v0.6.1Lars Hjemli2007-09-08
* Use git-1.5.3 as submoduleLars Hjemli2007-09-03
* Use git-1.5.2Lars Hjemli2007-05-20
* Added git as a submoduleLars Hjemli2007-05-11
an>builtin: Move echo space/nl handling into print_escape_strHerbert Xu Currently echocmd uses print_escape_str to do everything apart from printing the spaces/newlines separating its arguments. This patch moves the actual printing into print_escape_str as well using the format parameter. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-02builtin: Fix echo performance regressionHerbert Xu The commit d6c0e1e2ffbf7913ab69d51cc794d48d41c8fcb1 ("[BUILTIN] Handle embedded NULs correctly in printf") caused a performance regression in the echo built-in because every echo call now goes through the printf %b slow path where the string is always printed twice to ensure the space padding is correct in the presence of NUL characters. In fact this regression applies to printf %b as well. This is easily fixed by making printf %b take the fast path when no precision/field width modifiers are present. This patch also changes the second strchurnul call to strspn which generates slightly better code. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-02expand: Fix ghost fields with unquoted $@/$*Herbert Xu Harald van Dijk <harald@gigawatt.nl> wrote: > On 22/03/2018 22:38, Martijn Dekker wrote: >> Op 22-03-18 om 20:28 schreef Harald van Dijk: >>> On 22/03/2018 03:40, Martijn Dekker wrote: >>>> This patch fixes the bug that, given no positional parameters, unquoted >>>> $@ and $* incorrectly generate one empty field (they should generate no >>>> fields). Apparently that was a side effect of the above. >>> >>> This seems weird though. If you want to remove the recording of empty >>> regions because they are pointless, then how does removing them fix a >>> bug? Doesn't this show that empty regions do have an effect? Perhaps >>> they're not supposed to have any effect, perhaps it's a specific >>> combination of empty regions and something else that triggers some bug, >>> and perhaps that combination can no longer occur with your patch. >> >> The latter is my guess, but I haven't had time to investigate it. > > Looking into it again: > > When IFS is set to an empty string, sepc is set to '\0' in varvalue(). > This then causes *quotedp to be set to true, meaning evalvar()'s quoted > variable is turned on. quoted is then passed to recordregion() as the > nulonly parameter. > > ifsp->nulonly has a bigger effect than merely selecting whether to use > $IFS or whether to only split on null bytes: in ifsbreakup(), nulonly > also causes string termination to be suppressed. That's correct: that > special treatment is required to preserve empty fields in "$@" > expansion. But it should *only* be used when $@ is quoted: ifsbreakup() > takes nulonly from the last IFS region, even if it's empty, so having an > additional zero-length region with nulonly enabled causes confusion. > > Passing quoted by value to varvalue() and not attempting to modify it > should therefore, and in my quick testing does, also work to fix the > original $@ bug. You're right. The proper fix to this is to ensure that nulonly is not set in varvalue for $*. It should only be set for $@ when it's inside double quotes. In fact there is another bug while we're playing with $@/$*. When IFS is set to a non-whitespace character such as :, $* outside quotes won't remove empty fields as it should. This patch fixes both problems. Reported-by: Martijn Dekker <martijn@inlv.org> Suggested-by: Harald van Dijk <harald@gigawatt.nl> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-02parser: Allow newlines within parameter substitutionHerbert Xu On Fri, Mar 16, 2018 at 11:27:22AM +0800, Herbert Xu wrote: > On Thu, Mar 15, 2018 at 10:49:15PM +0100, Harald van Dijk wrote: > > > > Okay, it can be trivially modified to something that does work in other > > shells (even if it were actually executed), but gets rejected at parse time > > by dash: > > > > if false; then > > : ${$+ > > } > > fi > > That's just a bug in dash's parser with ${} in general, because > it bombs out without the if clause too: > > : ${$+ > } This patch fixes the parsing of newlines with parameter substitution. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-04-02expand: Fix bugs with words connected to the right of $@Herbert Xu On Sun, Mar 04, 2018 at 12:44:59PM +0100, Harald van Dijk wrote: > > command: set -- a ""; space=" "; printf "<%s>" "$@"$space > bash: <a><> > dash 0.5.8: <a>< > > dash 0.5.9.1: <a>< > > dash patched: <a><> This is actually composed of two bugs. First of all our tracking of quotemark is wrong so anything after "$@" becomes quoted. Once we fix that then the problem is that the first space character after "$@" is not recognised as an IFS. This patch fixes both. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-03-25Revert "[BUILTIN] Remove unnecessary restoration of format string in printf"Herbert Xu This reverts commit 7bb413255368e94395237d789f522891093c5774. The commit breaks printf with more than argument. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> 2018-03-22parser: Fix backquote support in here-document EOF markHerbert Xu