On Fri, Jul 3, 2015 at 10:53 PM, Duy Nguyen <[email protected]> wrote:
> On Sat, Jul 4, 2015 at 7:17 AM, Eric Sunshine <[email protected]> wrote:
>> COMMANDS
>> --------
>> +add <path> <branch>::
>> +
>> +Check out `<branch>` into a separate working directory, `<path>`, creating
>> +`<path>` if necessary. The new working directory is linked to the current
>> +repository, sharing everything except working directory specific files
>> +such as HEAD, index, etc. If `<path>` already exists, it must be empty.
>
> Side note, "must be empty" is an implementation limitation. I think
> the two-way merge employed by git-checkout can deal with dirty <path>
> and only perform the checkout if there is no data loss. But we can
> leave this for later.
Perhaps we should omit the bit about an existing but empty directory
for now? Like this:
Create `<path>` and checkout `<branch>` into it. The new working
directory is linked to the current repository, sharing everything
except working directory specific files such as HEAD, index, etc.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
