On Sun, Jan 20, 2013 at 6:57 PM, Rusty Russell wrote:
>
> I'm confused. The default argument is HEAD: what does it know about tag
> names?
Ugh. I actually thought that if you give it the tag name directly (as
the "end") it will use that.
But no. It figures it out with "git describe --exact" int
Linus Torvalds writes:
> On Sun, Jan 20, 2013 at 5:32 PM, Rusty Russell wrote:
>>
>> Due to the delay on git.kernel.org, git request-pull fails. It *looks*
>> like it succeeds, except the warning, but (as we learned last time I
>> screwed up), it doesn't put the branchname because it can't know
On Sun, Jan 20, 2013 at 6:00 PM, Junio C Hamano wrote:
>
> What you mean by "corrupt" is not clear to me
Some versions would just silently change the actual name you were using.
So if you said "for-linus", it might change it to "linus", just
because that branch happened to have the same SHA1 com
Linus Torvalds writes:
> On Sun, Jan 20, 2013 at 5:32 PM, Rusty Russell wrote:
>>
>> Due to the delay on git.kernel.org, git request-pull fails. It *looks*
>> like it succeeds, except the warning, but (as we learned last time I
>> screwed up), it doesn't put the branchname because it can't know
On Sun, Jan 20, 2013 at 5:32 PM, Rusty Russell wrote:
>
> Due to the delay on git.kernel.org, git request-pull fails. It *looks*
> like it succeeds, except the warning, but (as we learned last time I
> screwed up), it doesn't put the branchname because it can't know.
I think this should be fixed
5 matches
Mail list logo
