git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Stéphane Klein" <contact@stephane-klein.info>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Feature request: use relative path in worktree config files
Date: Sun, 9 Oct 2016 13:39:36 +0200	[thread overview]
Message-ID: <CADKxhpft56eu1_m70PGi3FPTeX7bS0L=WSe9yKZfLc94N7LsUA@mail.gmail.com> (raw)
In-Reply-To: <CACsJy8DGvyWz2_VBsEfmDWOPGUGAUhKYhCa1qLEMcOdn83ocSQ@mail.gmail.com>

2016-10-09 13:37 GMT+02:00 Duy Nguyen <pclouds@gmail.com>:
> On Sun, Oct 9, 2016 at 6:22 PM, Stéphane Klein
> <contact@stephane-klein.info> wrote:
>> 2016-10-09 13:11 GMT+02:00 Duy Nguyen <pclouds@gmail.com>:
>>>> 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
>>>
>>> I think the common way of dealing with this in docker is put things in
>>> the same path where it actually is outside docker. If you have stuff
>>> at /path/to/foo, then you create the same /path/to/foo inside docker
>>> and bind the data to that path. Does that work?
>>
>> It's not always possible. I can't in my project.
>>
>> I think there are some pros and some cons for relative path and absolute path.
>> Maybe append a "--relative" option with `git worktree add` ?
>>
>> I've converted all path to relative and all work with success.
>>
>> What do you think to append this --relative option.
>
> Patches are welcome.

Thanks :)

  reply	other threads:[~2016-10-09 11:40 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
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 [this message]
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='CADKxhpft56eu1_m70PGi3FPTeX7bS0L=WSe9yKZfLc94N7LsUA@mail.gmail.com' \
    --to=contact@stephane-klein.info \
    --cc=git@vger.kernel.org \
    --cc=pclouds@gmail.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).