Re: What's in git.git
- From
sean <seanlkml@sympatico.ca>
- Date
- Feb 9, 2006, 08:09 UTC
- Message-ID
- <BAYC1-PASMTP1142DA49F5BC7B7B42B22FAE030@CEZ.ICE>
- In-Reply-To
- <7vslqtf2p1.fsf@assigned-by-dhcp.cox.net>
On Wed, 08 Feb 2006 22:47:54 -0800 Junio C Hamano <junkio@cox.net> wrote:
Show 8 quoted lines
> One *major* change I am thinking about doing is to change my > workflow a bit. So far, the proposed updates branch "pu" was > almost impossible to follow unless you are really a devoted git > developer, because it is always rebased to the latest master and > then topic branches are merged onto it. While that keeps the > number of unnecessary merge nodes between master and pu to the > minimum, it actively discouraged for the branch to be followed > by developers.
I've always followed it okay by just using "git branch -d pu" each time before pulling from you. Your "next" branch does sound like an improvement though.
Sean