mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Ingo Molnar <mingo@elte.hu>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Linus <torvalds@linux-foundation.org>
Subject: Re: linux-next: Tree for April 9
Date: Thu, 10 Apr 2008 10:45:49 +1000	[thread overview]
Message-ID: <20080410104549.c2e1b645.sfr@canb.auug.org.au> (raw)
In-Reply-To: <47FCF50E.9090703@s5r6.in-berlin.de>

[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]

Hi Stefan,

On Wed, 09 Apr 2008 18:55:42 +0200 Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
>
> Stephen Rothwell wrote:
> > There were a few merge conflicts (fairly trivial) and couple of build
> > failures (notified).  There is a know build failure with powerpc
> > allyesconfig.  Below is a summary of the state of the merge.
> ...
> > Merging ieee1394/for-next
> > CONFLICT (content): Merge conflict in lib/Kconfig.debug
> 
> Would it be safe for me (and preferred by you) to merge sched/for-akpm
> into ieee1394/for-next to resolve this conflict until next mainline merge?

Actually, no, as sched/for-akpm gets rebased sometimes.  I only have to
fix these trivial conflicts once as "git rerere" remembers the fix for me
and they are so trivial that Linus will probably fix them the same way
when he finally merges your tree.  Also, there is the possibility that he
will merge your tree before sched/for-akpm ...

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-04-10  0:46 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-09  8:53 Stephen Rothwell
     [not found] ` <d711229d0804090400p1c92a158j381b86e207a6f38a@mail.gmail.com>
2008-04-09 11:09   ` Stephen Rothwell
2008-04-09 11:27     ` Stephen Rothwell
2008-04-09 11:26       ` Jacek Luczak
2008-04-09 11:34         ` Ingo Molnar
2008-04-09 11:55           ` Jacek Luczak
2008-04-09 12:01           ` Ingo Molnar
2008-04-09 11:31       ` Ingo Molnar
2008-04-09 14:50         ` Cyrill Gorcunov
2008-04-09 15:03           ` Ingo Molnar
2008-04-09 15:18             ` Cyrill Gorcunov
2008-04-09 16:55 ` Stefan Richter
2008-04-10  0:45   ` Stephen Rothwell [this message]
2008-04-10  6:52   ` Ingo Molnar
2008-04-10  7:44     ` Stephen Rothwell
2008-04-10  7:52       ` debug Kconfig option (was Re: linux-next: Tree for April 9) Stefan Richter
2008-04-10  9:51         ` Ingo Molnar
2008-04-10 19:05           ` [PATCH linux1394-2.6.git] firewire: fw-ohci: add option for remote debugging - amendment Stefan Richter
2008-04-10 22:08             ` Stefan Richter
2008-04-10 15:01         ` debug Kconfig option (was Re: linux-next: Tree for April 9) Randy Dunlap
2008-04-10  9:48       ` linux-next: Tree for April 9 Ingo Molnar
2008-04-10 19:02         ` Stefan Richter
2008-04-10  9:39 ` [BUG] linux-next: Tree for April 9 warning on CC_STACKPROTECTOR, followed by kernel panic Kamalesh Babulal
2008-04-10 10:14   ` Jacek Luczak
2008-04-10 10:51     ` Kamalesh Babulal
2008-04-10 10:58       ` Jacek Luczak
2008-04-10 11:47   ` Stephen Rothwell
2008-04-11  9:45     ` Ingo Molnar
2009-04-09  6:33 linux-next: Tree for April 9 Stephen Rothwell
2009-04-11  6:11 ` Andrew Morton
2009-04-11 11:09   ` Mauro Carvalho Chehab
2009-04-11 12:05     ` Stephen Rothwell
2010-04-09  3:34 Stephen Rothwell

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=20080410104549.c2e1b645.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=stefanr@s5r6.in-berlin.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

all inboxes | Powered by JetHome®