git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Olivier Marin <dkr+ml.git@free.fr>
Cc: "git list" <git@vger.kernel.org>,
	"Luciano Rocha" <luciano@eurotux.com>,
	pascal@obry.net, "Pierre Habouzit" <madcoder@debian.org>,
	"Kristian Høgsberg" <krh@redhat.com>
Subject: Re: [PATCH] files given on the command line are relative to $cwd
Date: Wed, 06 Aug 2008 13:19:07 -0700	[thread overview]
Message-ID: <7vtzdxnbgk.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <489A061B.7010508@free.fr> (Olivier Marin's message of "Wed, 06 Aug 2008 22:14:19 +0200")

Olivier Marin <dkr+ml.git@free.fr> writes:

> Junio C Hamano a écrit :
>>  
>>  static int parse_and_validate_options(int argc, const char *argv[],
>> -				      const char * const usage[])
>> +				      const char * const usage[],
>> +				      const char *prefix)
>>  {
>>  	int f = 0;
>>  
>>  	argc = parse_options(argc, argv, builtin_commit_options, usage, 0);
>> +	logfile = parse_options_fix_filename(prefix, logfile);
>
> It breaks the "git commit -F -" case, no?

Does it?  Ah, yeah, t7500 #15 does not go down to a subdirectory.

  reply	other threads:[~2008-08-06 20:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-06 10:30 something fishy with Git commit and log from file Pascal Obry
2008-08-06 10:44 ` Luciano Rocha
2008-08-06 11:01   ` Pascal Obry
2008-08-06 15:38     ` Junio C Hamano
2008-08-06 16:28       ` Pascal Obry
2008-08-06 16:50         ` Junio C Hamano
2008-08-06 17:08           ` Pascal Obry
2008-08-06 18:43           ` [PATCH] files given on the command line are relative to $cwd Junio C Hamano
2008-08-06 20:14             ` Olivier Marin
2008-08-06 20:19               ` Junio C Hamano [this message]
2008-08-06 20:59                 ` Junio C Hamano
2008-08-06 20:40             ` Pierre Habouzit
2008-08-07  8:45             ` Samuel Tardieu
2008-08-07  9:03               ` Luciano Rocha
2008-08-07  9:47                 ` 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=7vtzdxnbgk.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=dkr+ml.git@free.fr \
    --cc=git@vger.kernel.org \
    --cc=krh@redhat.com \
    --cc=luciano@eurotux.com \
    --cc=madcoder@debian.org \
    --cc=pascal@obry.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).