1 |
On Tue, Jul 30, 2013 at 2:47 AM, Ciaran McCreesh |
2 |
<ciaran.mccreesh@××××××××××.com> wrote: |
3 |
> On Mon, 29 Jul 2013 22:27:31 -0400 |
4 |
> Rich Freeman <rich0@g.o> wrote: |
5 |
>> On Mon, Jul 29, 2013 at 10:07 PM, Ulrich Mueller <ulm@g.o> |
6 |
>> wrote: |
7 |
>> > Is the history from the v0.26.0 tag to the tip of the branch linear? |
8 |
>> > If it contains merge commits, then git format-patch / git am isn't |
9 |
>> > guaranteed to work. |
10 |
>> |
11 |
>> There are branches. There is obviously /A/ linear path from the tag |
12 |
>> to the head (it is in the log) |
13 |
> |
14 |
> The log doesn't give you a linear path. Use --decorate --graph to |
15 |
> avoid the illusion. |
16 |
|
17 |
Understood. I think we're just quipping over the definition of |
18 |
"linear path" though. |
19 |
|
20 |
If having a linear path from A to B means that these nodes are |
21 |
connected and there is exactly one way to traverse the graph from A to |
22 |
B then there is not a linear path. If having a linear path from A to |
23 |
B means that these nodes are connected, and thus there is at least one |
24 |
way to traverse the graph from A to B without revisiting any nodes, |
25 |
then there is a linear path. |
26 |
|
27 |
Using the latter definition, a linear path exists if one node shows up |
28 |
in a git log started from the other. Using the former definition, you |
29 |
need to use --decorate --graph as you suggest. |
30 |
|
31 |
Rich |