public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@perex.cz>,
	ALSA development <alsa-devel@alsa-project.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [alsa-devel] HG -> GIT migration
Date: Thu, 22 May 2008 22:43:04 +0200	[thread overview]
Message-ID: <4835DAD8.2090204@keyaccess.nl> (raw)
In-Reply-To: <20080522112412.4a8406fd.sfr@canb.auug.org.au>

On 22-05-08 03:24, Stephen Rothwell wrote:

> Linux-next is rebuilt every day based on Linus' current kernel.  I merge
> all the trees I have been told about and fixup minor conflicts (sometimes
> reverting commits, sometimes applying patches).  So everyday, linux-next
> is completely new.  I do not care if the trees I am merging get rebased.

This means you're going to redo all those (same) minor conflict fixups 
each day again, doesn't it? Or do you pass the fixups back to (one of) 
the conflicting trees?

> I have only had a couple of occasions when the merge conflicts were so
> bad that I had to drop a whole tree, but they were fixed up the next day.
> 
> Linux-next has only one downstream - Andrew's mm tree and he bases on a
> particular day's linux-next tree each time he rebuilds mm.  Testers just
> need to take the complete tree (which isn't too bad if you are using git
> since all the linux-next trees share a lot of objects).
> 
> Does that answer your question?

But yes, it does, thanks.

Rene



  reply	other threads:[~2008-05-22 20:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.61.0805201314190.1798@tm8103-a.perex-int.cz>
     [not found] ` <200805211430.06653.linux@audioscience.com>
     [not found]   ` <Pine.LNX.4.61.0805210805080.1798@tm8103-a.perex-int.cz>
     [not found]     ` <s5hve18vtml.wl%tiwai@suse.de>
     [not found]       ` <483415E7.5080402@keyaccess.nl>
     [not found]         ` <s5hfxsbx27f.wl%tiwai@suse.de>
2008-05-21 13:04           ` [alsa-devel] HG -> GIT migration Rene Herman
2008-05-21 13:48             ` Jaroslav Kysela
2008-05-21 14:40               ` Rene Herman
2008-05-21 14:52                 ` Takashi Iwai
2008-05-21 15:29                   ` Rene Herman
2008-05-22  1:24                     ` Stephen Rothwell
2008-05-22 20:43                       ` Rene Herman [this message]
2008-05-22 23:40                         ` Stephen Rothwell
2008-05-21 14:47             ` Takashi Iwai
2008-05-21 15:40               ` Rene Herman
2008-05-21 16:02                 ` Takashi Iwai
2008-05-21 16:16                   ` Linus Torvalds
2008-05-21 16:51                     ` Takashi Iwai
2008-05-21 17:43                       ` Linus Torvalds
2008-05-21 18:11                         ` Linus Torvalds
2008-05-21 18:25                           ` david
2008-05-21 18:39                             ` Linus Torvalds
2008-05-21 18:49                             ` Takashi Iwai
2008-05-21 18:47                         ` Takashi Iwai
2008-05-21 19:02                           ` Linus Torvalds
2008-05-21 21:08                             ` Takashi Iwai
2008-05-22 14:23               ` Dmitry Torokhov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4835DAD8.2090204@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=sfr@canb.auug.org.au \
    --cc=tiwai@suse.de \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox