Ramkumar Ramachandra writes:
> On Matthieu's note, I have a comment: symbolic refs are an absolute
> dead end. We didn't think of it from the start, and it's too late
> now. Do NOT go there: from my investigation, I believe that hooking
> up everything to the revision parser is the way forward.
[joining the discussion late; was travelling]
Duy Nguyen wrote:
> git co long-branch-name
> git diff A/@
> git reset --hard A/@
In this form, this looks highly inconsistent. You have to decide if
you want @ to resolve to the current branch name or HEAD. Our current
@-proposal makes @@{1} displa
On Sat, May 4, 2013 at 10:26 AM, Duy Nguyen wrote:
> On Sat, May 4, 2013 at 5:09 AM, Matthieu Moy
> wrote:
>> The A/@ could make sense, but I'm wondering whether we're taking the
>> direction of implementing some kind of Brainfuck dialect in Git revision
>> specifiers. I'm not sure we want to add
On Sat, May 4, 2013 at 5:09 AM, Matthieu Moy
wrote:
> The A/@ could make sense, but I'm wondering whether we're taking the
> direction of implementing some kind of Brainfuck dialect in Git revision
> specifiers. I'm not sure we want to add more special characters here and
> there with subtly diffe
Junio C Hamano writes:
> Duy Nguyen writes:
>
>> My setup is a bit peculiar where I do git development on three
>> different machines. Say I updated branch long-branch-name on machine
>> A. Then I continue my work on machine B. I would want to hard reset
>> that long-branch-name on machine B bef
Duy Nguyen writes:
> On Fri, May 3, 2013 at 4:38 PM, Junio C Hamano wrote:
>> Junio C Hamano writes:
>>
>>> Duy Nguyen writes:
>>>
My setup is a bit peculiar where I do git development on three
different machines. Say I updated branch long-branch-name on machine
A. Then I contin
On Fri, May 3, 2013 at 4:38 PM, Junio C Hamano wrote:
> Junio C Hamano writes:
>
>> Duy Nguyen writes:
>>
>>> My setup is a bit peculiar where I do git development on three
>>> different machines. Say I updated branch long-branch-name on machine
>>> A. Then I continue my work on machine B. I wou
On Thu, May 2, 2013 at 9:51 PM, Duy Nguyen wrote:
> Hi,
>
> My setup is a bit peculiar where I do git development on three
> different machines. Say I updated branch long-branch-name on machine
> A. Then I continue my work on machine B. I would want to hard reset
> that long-branch-name on machine
Junio C Hamano writes:
> Duy Nguyen writes:
>
>> My setup is a bit peculiar where I do git development on three
>> different machines. Say I updated branch long-branch-name on machine
>> A. Then I continue my work on machine B. I would want to hard reset
>> that long-branch-name on machine B bef
Duy Nguyen writes:
> My setup is a bit peculiar where I do git development on three
> different machines. Say I updated branch long-branch-name on machine
> A. Then I continue my work on machine B. I would want to hard reset
> that long-branch-name on machine B before resuming my work. What I
> u
10 matches
Mail list logo