From: Junio C Hamano <gitster@pobox.com>
To: kevin brintnall <kbrint@rufus.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] added -C option to chdir() into another directory first
Date: Thu, 26 Feb 2009 13:50:37 -0800 [thread overview]
Message-ID: <7viqmwrhoy.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20090226204423.GA34377@rufus.net> (kevin brintnall's message of "Thu, 26 Feb 2009 14:44:23 -0600")
kevin brintnall <kbrint@rufus.net> writes:
> On Thu, Feb 26, 2009 at 12:35:57PM -0800, Junio C Hamano wrote:
>> kevin brintnall <kbrint@rufus.net> writes:
>>
>> > This allows things like 'git -C /somewhere pull' without specifying both
>> > --work-tree and --git-dir.
>>
>> Where should "git -C sub/dir apply this.patch" find the file "this.patch"?
>
> Good question.. It should probably come from the original $PWD. Maybe we
> should have "-C $DIR" simulate "--work-tree=$DIR --git=dir=$DIR/.git" ?
>
>> More generally, when "git -C there cmd arg1 arg2 arg3..." is run, how
>> should the implementation of cmd learn what to prefix arg$N with?
>
> I envisioned these two as equivalent:
>
> git -C $DIR something
> cd $DIR ; git something
If that is the case then I really do not see the point, other than "there
are _some_ tools like 'tar' that do it".
Sure, there are some tools that do many other things. So what?
next prev parent reply other threads:[~2009-02-26 21:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 20:11 [PATCH] added -C option to chdir() into another directory first kevin brintnall
2009-02-26 20:35 ` Junio C Hamano
2009-02-26 20:44 ` kevin brintnall
2009-02-26 21:50 ` Junio C Hamano [this message]
2009-02-27 14:21 ` Michael J Gruber
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=7viqmwrhoy.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kbrint@rufus.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 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.