All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Greg KH <greg@kroah.com>
Subject: Re: linux-next: i2c tree build failure
Date: Mon, 31 Aug 2009 14:15:46 +0200	[thread overview]
Message-ID: <20090831141546.6c52c7fb@hyperion.delvare> (raw)
In-Reply-To: <20090831215905.caadce2f.sfr@canb.auug.org.au>

On Mon, 31 Aug 2009 21:59:05 +1000, Stephen Rothwell wrote:
> On Mon, 31 Aug 2009 13:16:47 +0200 Jean Delvare <khali@linux-fr.org> wrote:
> > I am also surprised that I would have to tell you. What is the purpose
> > of the NEXT_BASE tag if you do not check for dependencies automatically?
> 
> I use the tag to choose the base when I import the quilt series into git.
> So far I have not needed to automate the ordering of the imports.
> 
> > Anyway, if you say git can deal with duplicate patches OK, then I think
> > I'll simply re-add the patch on my end. But I do not have a strong
> > opinion on this either, so if you prefer clean dependencies and
> > ordering without duplicate patches, it is just as easy for me to leave
> > the redundant patch out and restore the NEXT_BASE tag.
> 
> I prefer less dependencies (so you could put the patch back in), however,
> that means if Greg changes the patch, then we will have two slightly
> different versions to merge.  I can cope with that as well.

I've made sure my patch has the same name as Greg's, to make it easier
for you to spot duplicates.

> Just readd the patch :-)

OK, done. Hopefully the next merge window is coming soon now anyway, and
then the trouble with this specific patch will be solved.

-- 
Jean Delvare

  reply	other threads:[~2009-08-31 12:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-31  1:19 linux-next: i2c tree build failure Stephen Rothwell
2009-08-31 10:04 ` Jean Delvare
2009-08-31 11:03   ` Stephen Rothwell
2009-08-31 11:16     ` Jean Delvare
2009-08-31 11:59       ` Stephen Rothwell
2009-08-31 12:15         ` Jean Delvare [this message]
2009-08-31 12:21           ` 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=20090831141546.6c52c7fb@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.