Junio C Hamano wrote:
> Yeah, I am not strongly opposed to have something like that, and
> having a shorter (but not a single letter) option name might make it
> more attractive than A...B at least to new users.
I'm not married to the single character or tilde. What I'm saying is
that we should m
Jonathan Nieder writes:
>> And it does not match "git log origin...HEAD" which gives both sides
>> of the symmetric difference of the history. To match it, you have
>> to say "git log --right-only origin...HEAD" or something.
>
> I tend to use --left-right. All I meant is that with both diff an
Junio C Hamano wrote:
> And it does not match "git log origin...HEAD" which gives both sides
> of the symmetric difference of the history. To match it, you have
> to say "git log --right-only origin...HEAD" or something.
I tend to use --left-right. All I meant is that with both diff and
log, ..
Junio C Hamano wrote:
> And it does not match "git log origin...HEAD"
Exactly my problem. Inconsistency.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Jonathan Nieder writes:
> What would it mean for A..B to be treated as a revision range?
Nonsense is what it means ;-)
> Suppose I do a revision walk and come up with the commits x, y,
> and z. What is the resulting diff?
>
> The common syntax is just a mnemonic: in the same situations as I
>
Hi,
Ramkumar Ramachandra wrote:
>A..B and A...B do not correspond to the meaning
> specified in gitrevisions.txt. There's a note in the documentation
> saying this, but I'm very unhappy.
What would it mean for A..B to be treated as a revision range?
Suppose I do a revision
6 matches
Mail list logo
