Re: [PATCH 22/32] checkout: support checking out into a new working directory
- From
Philip Oakley <philipoakley@iee.org>
- Date
- Aug 31, 2014, 11:08 UTC
- Message-ID
- <64D6AA311E524C27A8B6EDE7A63489D7@PhilipOakley>
- In-Reply-To
- <CACsJy8ASW0xO3WzU7f+T4iDhjL=Y=C6K+Cvi-OWOnS16r=m+9Q@mail.gmail.com>
From: "Duy Nguyen" <pclouds@gmail.com>
Show 19 quoted lines
> On Sun, Aug 31, 2014 at 11:49 AM, Duy Nguyen <pclouds@gmail.com> > wrote: >> All checkouts share the same repository. Linked checkouts see the >> repository a bit different from the main checkout. When you perform >> the command >> >> ------------ >> git checkout --to <some-location> <some-branch> >> ------------ >> >> The checkout at <some-location> will have a unique id that is also >> the >> branch name (e.g. "<some-branch>"). A number may be appended to the >> id > > .. and I got my facts wrong. The above line should be: > > last component of <some-location>. A number may be appended to the id >
That's fine. Glad that we're on the same wavelength for the documentation.
Show 12 quoted lines
>> to make it unique. All worktree-specific files of this new checkout >> are in $GIT_DIR/repos/<unique-id> of the main checkout. So "HEAD" >> inside the linked checkout will be resolved to >> "$GIT_DIR/repos/<some-branch>/HEAD", while "HEAD" from the main > > s/<some-branch>/<unique-id>/ > >> checkout remains "$GIT_DIR/HEAD". > > > > --
Philip