Re: [ANNOUNCE] Git v2.0.0-rc0
- From
Jonathan Nieder <jrnieder@gmail.com>
- Date
- Apr 22, 2014, 22:11 UTC
- Message-ID
- <20140422221148.GD15516@google.com>
- In-Reply-To
- <xmqqy4yx2gz9.fsf@gitster.dls.corp.google.com>
Junio C Hamano wrote:
> Jonathan Nieder <jrnieder@gmail.com> writes:
Show 14 quoted lines
>> The documentation says >> >> --prefix=<prefix> >> >> ... >> >> Before Git 2.0, the default prefix was "" (no prefix). >> This meant that ... >> >> which suggests that I can use --prefix="" to mean no prefix. Perhaps >> it needs a note to suggest using '--prefix ""' instead? > > Is there another --option that takes an arbitrary user string that > could be an empty string (or will there be one in the future)?
In git in general, yes --- for example, 'git diff --src-prefix="" HEAD^' tells "git diff" to leave off the usual c/ prefix in the src filename it prints.
In git-svn, --trunk="" or --message="" might be meaningful, but not nearly as much as --prefix="".
Show 5 quoted lines
> If > that is the case, a better alternative might be to add an comment to > say that those with older Getopt::Long may have to use --option "" > instead of the --option="" form for any option whose value happens > to be an empty string to work around the command parser bug.
Another possibility would be to require Perl 5.8.9 or newer. It was released in 2008.
diff --git i/git-svn.perl w/git-svn.perl index 0a32372..ec7910d 100755 --- i/git-svn.perl +++ w/git-svn.perl @@ -1,7 +1,7 @@ #!/usr/bin/perl # Copyright (C) 2006, Eric Wong <normalperson@yhbt.net> # License: GPL v2 or later -use 5.008; +use 5.008_009; use warnings; use strict; use vars qw/ $AUTHOR $VERSION