From: "Frédéric Heitzmann" <frederic.heitzmann@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Need to set GIT_WORK_TREE when setting GIT_DIR !?
Date: Sat, 10 Mar 2012 14:23:52 +0100 [thread overview]
Message-ID: <4F5B55E8.4080000@gmail.com> (raw)
In-Reply-To: <7v4ntx4bol.fsf@alter.siamese.dyndns.org>
Le 10/03/2012 00:06, Junio C Hamano a écrit :
> Yes, to the question on the Subject line. But you can also say
>
> [core] worktree = /path/to/the/work/tree
>
> in $GIT_DIR/config. Make sure your $GIT_DIR/config does *NOT* say
> that the repository is a bare repository.
Thanks for clarification.
However man git-config says :
"If --git-dir or GIT_DIR is specified but none of --work-tree,
GIT_WORK_TREE and core.worktree is specified, the
current working directory is regarded as the top level of your working
tree."
Some more context on my precise problem :
I have a project, with source files managed with git.
I also use some Makefiles that I would like to manage with git _in a
separate repository_
$ GIT_DIR=<project_path>/.git git add some_file.c ...
$ GIT_DIR=<project_path>/.git_mk git add Makefile ...
Setting worktree in each GIT_DIR/config will fix that but I can't figure
out why current git implementation actually needs this.
--
Fred
next prev parent reply other threads:[~2012-03-10 13:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 22:51 Need to set GIT_WORK_TREE when setting GIT_DIR !? Frédéric Heitzmann
2012-03-09 23:06 ` Junio C Hamano
2012-03-10 13:23 ` Frédéric Heitzmann [this message]
2012-03-10 14:05 ` Nguyen Thai Ngoc Duy
2012-03-10 21:20 ` Junio C Hamano
[not found] ` <CALeToSVPWPwJTYxRgy0BW4TBfBJrb+LXC+QJDWjceQ=4f2_tRw@mail.gmail.com>
[not found] ` <CALeToSV6xx=Vfw8gRbmeKWDzcHFaYvgFhMqx5cwtCYKdASJptw@mail.gmail.com>
2012-03-11 21:13 ` Frédéric Heitzmann
2012-03-10 14:11 ` Jonathan Nieder
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=4F5B55E8.4080000@gmail.com \
--to=frederic.heitzmann@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).