Thibault Kruse writes:
>> I am not sure why you meant to treat (2) and (3) differently,
>> though. Care to elaborate?
>
> As in my example, git clone --branch does not accept all of (3).
That is a prime example of outside "checkout" we give a white lie to
show the most common to help beginner
Hi Junio,
On Mon, Feb 18, 2013 at 10:22 AM, Junio C Hamano wrote:
> Thibault Kruse writes:
>
>> Whenever a command description involves "" this can, depending
>> on the command, refer to
>> 1) a name that, when prepended with "refs/heads/", is a valid ref,
>> 2) a name that, when prepended with
Thibault Kruse writes:
> Whenever a command description involves "" this can, depending
> on the command, refer to
> 1) a name that, when prepended with "refs/heads/", is a valid ref,
> 2) a name that, when prepended with "refs/heads/" or "refs/tags", is a
> valid ref,
> 3) a name that, when prep
Hi Duy,
Looking closer at the rest of the docs, I guess it is consistent, but
not terribly helpful.
Throughout the docs (--help and man), it is never very clear what
objects a command
may accept or not. here is what I get from it:
Whenever a command description involves "" this can, depending
on
On Mon, Feb 18, 2013 at 2:13 AM, Thibault Kruse
wrote:
> Hi all,
>
> I notice that using git 1.8.3, I can call
> git clone repo1 repo2 --branch tagname
> with a tag, not a branch. Is this going to be a stable and documented feature?
There is a test for --branch=tag in t5601, so I say it's support
Hi all,
I notice that using git 1.8.3, I can call
git clone repo1 repo2 --branch tagname
with a tag, not a branch. Is this going to be a stable and documented feature?
cheers,
Thibault
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.k
6 matches
Mail list logo
