From: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
To: "Jeff King" <peff@peff.net>
Cc: "Maciej Pasternacki" <maciej@pasternacki.net>, git@vger.kernel.org
Subject: Re: [PATCH] -C/--chdir command line option
Date: Mon, 20 Oct 2008 20:59:46 +0700 [thread overview]
Message-ID: <fcaeb9bf0810200659p91acb1cj58be43d3ef1c3e15@mail.gmail.com> (raw)
In-Reply-To: <20081019131745.GA8643@coredump.intra.peff.net>
On 10/19/08, Jeff King <peff@peff.net> wrote:
> I'm not sure if the actual problem is related to the oft-discussed,
> unresolved work-tree startup woes, or is something much simpler to fix.
> I'll try to look closer later today.
I think all commands should be able to jump to worktree even if you
are outside work-tree. git-pull and similar commands are easy because
they don't take pathnames. The way pathnames are handled in git does
not make it easy for outside current working directory, because if old
cwd is outside worktree, the parameter "prefix" sent to those commands
become "../../blah/", not a real prefix anymore. If a command expects
an index pathname, then that prefix should be rejected. If they expect
a filesystem pathname, it can be used with care.
--
Duy
next prev parent reply other threads:[~2008-10-20 14:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 0:02 [PATCH] -C/--chdir command line option Maciej Pasternacki
2008-10-19 13:17 ` Jeff King
2008-10-19 13:47 ` Maciej Pasternacki
2008-10-19 14:16 ` Jeff King
2008-10-19 15:24 ` Maciej Pasternacki
2008-10-20 4:55 ` Junio C Hamano
2008-10-20 5:41 ` Junio C Hamano
2008-10-20 6:26 ` Alex Riesen
2008-10-20 12:57 ` Michael J Gruber
2008-10-20 13:59 ` Nguyen Thai Ngoc Duy [this message]
[not found] <DDFCD680-C477-4BE5-AB71-3F26048E26D1@pasternacki.net>
2008-10-20 7:28 ` Maciej Pasternacki
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=fcaeb9bf0810200659p91acb1cj58be43d3ef1c3e15@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=maciej@pasternacki.net \
--cc=peff@peff.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).