From: bill lam <cbill.lam@gmail.com>
To: git <git@vger.kernel.org>
Subject: tool and worktree
Date: Sun, 8 Feb 2009 11:44:06 +0800 [thread overview]
Message-ID: <20090208034406.GB7230@b2j> (raw)
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 .
tig : status view said, The status view requires a working tree
Can these be improved?
--
regards,
====================================================
GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
唐詩314 王昌齡 長信怨
奉帚平明金殿開 且將團扇共徘徊 玉顏不及寒鴉色 猶帶昭陽日影來
next reply other threads:[~2009-02-08 4:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-08 3:44 bill lam [this message]
2009-02-08 9:47 ` tool and worktree 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
-- 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=20090208034406.GB7230@b2j \
--to=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).