Jakub Narębski writes:
> P.S. From some StackOverflow questions the connection between "(no
> branch)" and detached HEAD is not clear for git newbies...
If _that_ is the problem you are really trying to address, the
output from recent Git already says "(detached from xx)" or
something, so I
W dniu 10.04.2013 16:45, Junio C Hamano pisze:
> Jakub Narębski writes:
>
>> Junio C Hamano wrote:
>>
>>> diff --git a/Documentation/glossary-content.txt
>>> b/Documentation/glossary-content.txt
>>> index f928b57..69c90d1 100644
>>> --- a/Documentation/glossary-content.txt
>>> +++ b/Documentatio
Jakub Narębski writes:
> Junio C Hamano wrote:
>
>> diff --git a/Documentation/glossary-content.txt
>> b/Documentation/glossary-content.txt
>> index f928b57..69c90d1 100644
>> --- a/Documentation/glossary-content.txt
>> +++ b/Documentation/glossary-content.txt
>> @@ -100,9 +100,22 @@ to point at
Junio C Hamano wrote:
> diff --git a/Documentation/glossary-content.txt
> b/Documentation/glossary-content.txt
> index f928b57..69c90d1 100644
> --- a/Documentation/glossary-content.txt
> +++ b/Documentation/glossary-content.txt
> @@ -100,9 +100,22 @@ to point at the new commit.
>
> [[def_deta
On Fri, Apr 5, 2013 at 11:19 AM, Junio C Hamano wrote:
> Add a blanket description to the glossary to cover them instead.
> The general principle is that operations to update the branch work
> and affect on the HEAD, while operations to update the information
s/work and affect on the/work on and
When we introduced the concept of "detached HEAD", we made sure that
commands that operate on the history of the current branch "just
work" in that state. They update the HEAD to point at the new
history without affecting any branch when the HEAD is detached, just
like they update the tip of the "
6 matches
Mail list logo
