* Bug: git log: boundary commits do not respect order (e.g. date-order, topo-order)
@ 2018-02-21 23:28 Josh Tepper
2018-02-21 23:56 ` Josh Tepper
0 siblings, 1 reply; 2+ messages in thread
From: Josh Tepper @ 2018-02-21 23:28 UTC (permalink / raw)
To: git
When using git log, boundary commits (ie, those commits added by
specifying --boundary) do not respect the order (e.g., --date-order,
--topo-order). Consider the following commit history, where number
indicates the order of the commit timestamps:
<view with a fixed with font! 3's ancestor is 1, 6's ancestors are 4,5>
0----1----2----5 <--A
\ \
3----4----6 <--B
Executing the following command:
$ git log --boundary --date-order ^A B
Should produce the following order (boundary commits shown with dashes):
6 -5 4 3 -1
However, it in fact produces:
6 4 3 -7 -1
Please advise.
Best,
~Josh
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Bug: git log: boundary commits do not respect order (e.g. date-order, topo-order)
2018-02-21 23:28 Bug: git log: boundary commits do not respect order (e.g. date-order, topo-order) Josh Tepper
@ 2018-02-21 23:56 ` Josh Tepper
0 siblings, 0 replies; 2+ messages in thread
From: Josh Tepper @ 2018-02-21 23:56 UTC (permalink / raw)
To: git
TYPO IN EXPECTED OUTPUT.
To avoid inevitable confusion, creating new thread "Bug: git log:
boundary commits do not respect order (e.g. date-order, topo-order)
2".
DON'T REPLY TO THIS MESSAGE. Instead reply to the new message
On Wed, Feb 21, 2018 at 6:28 PM, Josh Tepper <josh@clarifai.com> wrote:
> When using git log, boundary commits (ie, those commits added by
> specifying --boundary) do not respect the order (e.g., --date-order,
> --topo-order). Consider the following commit history, where number
> indicates the order of the commit timestamps:
>
> <view with a fixed with font! 3's ancestor is 1, 6's ancestors are 4,5>
> 0----1----2----5 <--A
> \ \
> 3----4----6 <--B
>
>
> Executing the following command:
>
> $ git log --boundary --date-order ^A B
>
> Should produce the following order (boundary commits shown with dashes):
> 6 -5 4 3 -1
>
> However, it in fact produces:
> 6 4 3 -7 -1
>
> Please advise.
>
> Best,
> ~Josh
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-02-21 23:57 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-02-21 23:28 Bug: git log: boundary commits do not respect order (e.g. date-order, topo-order) Josh Tepper
2018-02-21 23:56 ` Josh Tepper
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.