Thread (3 messages) 3 messages, 3 authors, 2006-01-09

Re: git pull on Linux/ACPI release tree

From: Johannes Schindelin <hidden>
Date: 2006-01-09 12:31:57
Also in: linux-acpi, lkml

Hi,

On Mon, 9 Jan 2006, Martin Langhoff wrote:
In a sense we are still exploring possible/desirable workflows and what 
the missing pieces are. And yes, some thing don't quite make sense from 
the outside, perhaps because they just don't or because we arent' 
explaining them very well.
Maybe what is needed here is this:

T1 - T2 .. Tn .. Tp
  \         \      \
   \         M1     M2
    \       /      /
     B1 .. Bm .. Bo

where T1..Tp are the upstream commits, B1..Bo are the local commits, and
M1.. are the test merges just to make sure nothing breaks?

As long as the Mx commits resolve automatically, no need for an explicit 
merge in the Bx commits, since a pull from B into T will just recreate an 
Mx as next commit in T.

Kind of "throw away merge".

Ciao,
Dscho
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help