From: "Stéphane Klein" <contact@stephane-klein.info>
To: git@vger.kernel.org
Subject: Re: Feature request: use relative path in worktree config files
Date: Sat, 8 Oct 2016 21:54:55 +0200 [thread overview]
Message-ID: <CADKxhpcKOX4RkpbkA8t_6MUh3DttPgwA-YquMkuHkS3C2FR6xg@mail.gmail.com> (raw)
In-Reply-To: <CADKxhpe3S4L9CPV9yxh2yhrtJMa9wyZAPC45u_S=RiuzY1Xrkg@mail.gmail.com>
I've write a small tool in Golang to fix this issue:
https://github.com/harobed/fix-git-worktree
2016-10-08 11:35 GMT+02:00 Stéphane Klein <contact@stephane-klein.info>:
> Hi,
>
> "git worktree add" write absolute path in ".git/gitdir"
>
> The code source is here
> https://git.kernel.org/cgit/git/git.git/tree/builtin/worktree.c?h=v2.10.1#n256
>
> Is it possible to use relative path in this config files:
>
> * [main_worktree]/.git/worktrees/[worktree_foobar]/gitdir
> * [worktree_foobar]/.git
>
> Why:
>
> 1. I configure worktree on my host
> 2. next I use this git working copy in Docker with volume share
> 3. next I've some git error in Docker because config files use absolute path
>
> Best regards,
> Stéphane
> --
> Stéphane Klein <contact@stephane-klein.info>
> blog: http://stephane-klein.info
> cv : http://cv.stephane-klein.info
> Twitter: http://twitter.com/klein_stephane
--
Stéphane Klein <contact@stephane-klein.info>
blog: http://stephane-klein.info
cv : http://cv.stephane-klein.info
Twitter: http://twitter.com/klein_stephane
next prev parent reply other threads:[~2016-10-08 19:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-08 9:35 Feature request: use relative path in worktree config files Stéphane Klein
2016-10-08 19:54 ` Stéphane Klein [this message]
2016-10-09 11:11 ` Duy Nguyen
2016-10-09 11:22 ` Stéphane Klein
2016-10-09 11:37 ` Duy Nguyen
2016-10-09 11:39 ` Stéphane Klein
2016-10-10 18:36 ` Junio C Hamano
2016-10-11 11:16 ` Duy Nguyen
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=CADKxhpcKOX4RkpbkA8t_6MUh3DttPgwA-YquMkuHkS3C2FR6xg@mail.gmail.com \
--to=contact@stephane-klein.info \
--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).