From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
To: git@vger.kernel.org
To: git@vger.kernel.org
Cc: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
bill lam <cbill.lam@gmail.com>
Subject: Re: tool and worktree
Date: Mon, 9 Feb 2009 18:49:41 +0100 [thread overview]
Message-ID: <1234201781-5537-1-git-send-email-giuseppe.bilotta@gmail.com> (raw)
In-Reply-To: <20090209161907.GA953@neumann>
On Sunday 08 February 2009 20:25, Shawn O. Pearce wrote:
> bill lam <cbill.lam@gmail.com> wrote:
>> I track /etc using a config
>>
>> [core]
>> repositoryformatversion = 0
>> filemode = true
>> bare = false
>> worktree = /etc
>> logAllRefUpdates = true
>> excludesfile =
>>
>> But that can not be handled by tools,
>>
>> git gui : cannot use funny .git directory .
>
> If someone sends patches for git-gui, maybe. This use case of
> different repository and worktree isn't very common for git-gui
> so it doesn't support it.
I came across the same problem. I also sent a tentative patchset to
solve the problem about 12 hours ago:
http://thread.gmane.org/gmane.comp.version-control.git/109035
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2009-02-09 17:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 14:08 [RFC/RFH] Fun things with git-notes, or: patch tracking backwards Thomas Rast
2009-02-09 16:19 ` SZEDER Gábor
2009-02-09 16:29 ` Thomas Rast
2009-02-09 17:49 ` Giuseppe Bilotta [this message]
2009-02-10 22:42 ` Thomas Rast
2009-02-10 22:52 ` Junio C Hamano
2009-02-10 22:59 ` Junio C Hamano
2009-02-10 23:12 ` Thomas Rast
2009-02-10 23:30 ` Junio C Hamano
2009-02-11 22:52 ` Thomas Rast
2009-02-11 22:58 ` Thomas Rast
-- strict thread matches above, loose matches on Subject: below --
2009-02-08 3:44 tool and worktree bill lam
2009-02-08 9:47 ` Jonas Fonseca
2009-02-09 1:17 ` Jonas Fonseca
2009-02-09 2:15 ` bill lam
2009-02-09 3:23 ` Jonas Fonseca
2009-02-08 19:25 ` Shawn O. Pearce
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=1234201781-5537-1-git-send-email-giuseppe.bilotta@gmail.com \
--to=giuseppe.bilotta@gmail.com \
--cc=cbill.lam@gmail.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).