From: Lars Ingebrigtsen <larsi@gnus.org>
To: Gregor Zattler <grfz@gmx.de>
Cc: 5344@debbugs.gnu.org
Subject: bug#5344: 23.1.91; bug/wish: vc does not honour GIT_DIR / GIT_WORK_TREE environment variables
Date: Sat, 23 Nov 2019 14:03:33 +0100 [thread overview]
Message-ID: <87imnaoica.fsf@gnus.org> (raw)
In-Reply-To: <20100110223940.GB4845@shi.workgroup> (Gregor Zattler's message of "Sun, 10 Jan 2010 23:39:40 +0100")
Gregor Zattler <grfz@gmx.de> writes:
> (defun vc-git-root (file)
> - (vc-find-root file ".git"))
> +(if (getenv "GIT_DIR")
> + (getenv "GIT_WORK_TREE")
> + (vc-find-root file ".git")))
As far as I can tell by skimming vc-git.el, functionality like this has
not been added during the intervening years. The use case it:
> I use bare git repositories for version contol of some dotfiles.[1] This
> means that the repository ist *not* in a .git directory which is part of
> the working directorys hirarchy. Instead the environment variable
> GIT_DIR indicates the location of the repository and the environment
> variable GIT_WORK_TREE indicates the working directory.
We wouldn't want to add this in the form suggested above, but it does
sound like a useful feature, if I understand it correctly. But I don't
quite see how you'd tie a specific location to a specific GIT_DIR value,
so I don't see how this would work in general. Perhaps fall back on
GIT_DIR/GIR_WORK_TREE if vc-git-root returns nil would be reasonable?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-11-23 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-09 1:49 bug#5344: 23.1.91; bug/wish: vc does not honour GIT_DIR / GIT_WORK_TREE environment variables Gregor Zattler
2010-01-09 19:29 ` Dan Nicolaescu
2010-01-10 11:23 ` Gregor Zattler
2010-01-10 22:39 ` Gregor Zattler
2019-11-23 13:03 ` Lars Ingebrigtsen [this message]
[not found] ` <87wobpfnpq.fsf@len.workgroup>
2019-11-24 21:46 ` Lars Ingebrigtsen
2019-12-01 10:53 ` Gregor Zattler
2019-12-01 16:37 ` Robert Pluim
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87imnaoica.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=5344@debbugs.gnu.org \
--cc=grfz@gmx.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).