From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rene Herman Subject: Re: HG -> GIT migration Date: Wed, 21 May 2008 17:40:33 +0200 Message-ID: <48344271.3090700@keyaccess.nl> References: <200805211430.06653.linux@audioscience.com> <483415E7.5080402@keyaccess.nl> <48341DF5.4090307@keyaccess.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from smtpq2.groni1.gr.home.nl (smtpq2.groni1.gr.home.nl [213.51.130.201]) by alsa0.perex.cz (Postfix) with ESMTP id CA26324391 for ; Wed, 21 May 2008 17:38:03 +0200 (CEST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Takashi Iwai Cc: alsa-devel@alsa-project.org, Linus Torvalds , Linux Kernel List-Id: alsa-devel@alsa-project.org On 21-05-08 16:47, Takashi Iwai wrote: > Theoretically we can work only using merges. However, the resultant > tree will look too complex with lots of merge points at the time of > the next merge window. This is also a nightmare for bisecting. Thus, > most subsystem trees do rebase before the merge window in practice, > AFAIK. > > It'd be appreciated if someone can tell me any good workflow to keep a > good-shaped tree without rebasing... Over here: http://lkml.org/lkml/2008/5/17/203 Linus suggests to just not do many merges from upstream -- basically only at releases. I'm only looking at and experiencing things from the limited viewpoint of a leaf node though so I'll shut up for a bit first now as this might not be helpful. Rene.