git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thierry Moreau <thierry.moreau@connotech.com>
To: Bryan Turner <bturner@atlassian.com>
Cc: Git Users <git@vger.kernel.org>
Subject: Re: Self-inflicted "abort" in a newbie attempt at read-only exploration of a cloned repository?
Date: Fri, 06 Apr 2018 00:50:40 +0000	[thread overview]
Message-ID: <5AC6C460.7060005@connotech.com> (raw)
In-Reply-To: <CAGyf7-GZgTpYXt4s+NURABYLBr8HQAZWxsrpLLVKnsOf2SYcBQ@mail.gmail.com>

On 05/04/18 11:34 PM, Bryan Turner wrote:
> On Thu, Apr 5, 2018 at 4:18 PM, Bryan Turner <bturner@atlassian.com> wrote:
>>
>> So passing --work-tree tells Git where to store your _files_, but it's
>> still using the same .git directory.
>>
>> If your goal is to have worktrees for various versions, that implies
>> the git worktree [1] command might be more along the lines of what
>> you're looking for. An invocation based on above might look like this:
>> $ git -C linux-stable/ worktree add $PWD/tmp/ checkout linux-4.15.y
>
> Apologies, I didn't mean to have the "checkout" in that.
> $ git -C linux-stable/ worktree add $PWD/tmp/ linux-4.15.y
>
>>
>> That should leave linux-4.16.y checked out in linux-stable, while
>> creating a full work tree in $PWD/tmp that has 4.15.y checked out.
>>
>> Note that worktree is a newer git command. 2.17 has it, but old
>> versions like 2.1 won't.
>>
>> [1] https://git-scm.com/docs/git-worktree
>>
>> Hope this helps!

For sure, it helps! Thanks.

- Thierry


  reply	other threads:[~2018-04-06  0:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05 19:42 Self-inflicted "abort" in a newbie attempt at read-only exploration of a cloned repository? Thierry Moreau
2018-04-05 23:18 ` Bryan Turner
2018-04-05 23:34   ` Bryan Turner
2018-04-06  0:50     ` Thierry Moreau [this message]
2018-04-06 19:56   ` Jeff King
2018-04-06 20:27     ` Thierry Moreau

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=5AC6C460.7060005@connotech.com \
    --to=thierry.moreau@connotech.com \
    --cc=bturner@atlassian.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).