From: Jonas Fonseca <jonas.fonseca@gmail.com>
To: git <git@vger.kernel.org>
Subject: Re: tool and worktree
Date: Mon, 9 Feb 2009 02:17:50 +0100 [thread overview]
Message-ID: <2c6b72b30902081717q35fd4ba0k6ff5b1be8cd5ef2c@mail.gmail.com> (raw)
In-Reply-To: <2c6b72b30902080147u61412b04w24baa0e5fdc29584@mail.gmail.com>
On Sun, Feb 8, 2009 at 10:47, Jonas Fonseca <jonas.fonseca@gmail.com> wrote:
> It might be as
> simple as setting the GIT_DIR environment to getcwd() + output of
> git-rev-parse --git-dir and then chdir() to core.worktree.
I have pushed a lightly tested patch that does something like this ...
--
Jonas Fonseca
next prev parent reply other threads:[~2009-02-09 1:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-08 3:44 tool and worktree bill lam
2009-02-08 9:47 ` Jonas Fonseca
2009-02-09 1:17 ` Jonas Fonseca [this message]
2009-02-09 2:15 ` bill lam
2009-02-09 3:23 ` Jonas Fonseca
2009-02-08 19:25 ` Shawn O. Pearce
-- strict thread matches above, loose matches on Subject: below --
2009-02-09 16:19 [RFC/RFH] Fun things with git-notes, or: patch tracking backwards SZEDER Gábor
2009-02-09 17:49 ` tool and worktree Giuseppe Bilotta
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=2c6b72b30902081717q35fd4ba0k6ff5b1be8cd5ef2c@mail.gmail.com \
--to=jonas.fonseca@gmail.com \
--cc=git@vger.kernel.org \
/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).