All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Kyle J. McKay" <mackyle@gmail.com>,
	Johan Herland <johan@herland.net>,
	git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git v2.0.0-rc0
Date: Tue, 22 Apr 2014 15:11:48 -0700	[thread overview]
Message-ID: <20140422221148.GD15516@google.com> (raw)
In-Reply-To: <xmqqy4yx2gz9.fsf@gitster.dls.corp.google.com>

Junio C Hamano wrote:
> Jonathan Nieder <jrnieder@gmail.com> writes:

>> 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="".

>                                                                 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

  reply	other threads:[~2014-04-22 22:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-18 19:37 [ANNOUNCE] Git v2.0.0-rc0 Junio C Hamano
2014-04-19  1:13 ` Johan Herland
2014-04-19  7:20   ` Junio C Hamano
2014-04-20 19:08 ` Felipe Contreras
2014-04-20 21:14   ` Junio C Hamano
2014-04-22 11:16 ` Kyle J. McKay
2014-04-22 18:58   ` Jonathan Nieder
2014-04-22 20:12     ` Junio C Hamano
2014-04-22 21:00       ` Jonathan Nieder
2014-04-22 21:26         ` Junio C Hamano
2014-04-22 22:11           ` Jonathan Nieder [this message]
2014-04-22 22:25             ` brian m. carlson
2014-04-22 22:47               ` Junio C Hamano
2014-04-23  7:33                 ` Johan Herland
2014-04-23 16:40                   ` Junio C Hamano
2014-04-22 19:56   ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140422221148.GD15516@google.com \
    --to=jrnieder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=johan@herland.net \
    --cc=mackyle@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.