|
From: | Robert Anderson |
Subject: | Re: [Gnu-arch-users] Cascading patchlogs with star-merge |
Date: | Sun, 21 Mar 2004 11:27:18 -0800 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4.1) Gecko/20031008 |
James Blackwell wrote:
Commit patch-N in archive 1 star-merge from archive 1 into archive 2, then commit, creating patch-M there star-merge from archive 2 into archive 1, commit creating patch-N+1 there star-merge from archive 1 into archive 2, creating patch-M+1 ... etc This can go on forever, and the only things getting added to the working copies each time are patch logs. I was looking to automate the sharing of patches like this, but found that it never stopped.Its up to you and him to notice that the only thing that changed was patch logs. If you star merge somebody and the only change you see is patchlogs, then why would you commit that to your tree?
Why should I have to merge it to find out it's something I didn't want? Bob
[Prev in Thread] | Current Thread | [Next in Thread] |