From: "Shawn O. Pearce" <spearce@spearce.org>
To: bill lam <cbill.lam@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: tool and worktree
Date: Sun, 8 Feb 2009 11:25:28 -0800 [thread overview]
Message-ID: <20090208192528.GC30557@spearce.org> (raw)
In-Reply-To: <20090208034406.GB7230@b2j>
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.
On Windows with some versions of Tcl/Tk I've had trouble in the
past with Git finding the repository when forked out of the wish
process. To work around it I just required that the repository
be in ".git".
Have you tried making /etc/.git a symlink to the real repository?
BTW, tracking /etc/ in git won't track permissions and ownership
so restoring /etc from git isn't enough on its own. Usually I
use some sort of shell script to copy /etc to another location
and check it into git, and a different script to go the other way,
with that script handling mode and ownership as it goes.
--
Shawn.
next prev parent reply other threads:[~2009-02-08 19:27 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
2009-02-09 2:15 ` bill lam
2009-02-09 3:23 ` Jonas Fonseca
2009-02-08 19:25 ` Shawn O. Pearce [this message]
-- 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=20090208192528.GC30557@spearce.org \
--to=spearce@spearce.org \
--cc=cbill.lam@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).