linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: Status of arm-soc.git for 3.2
Date: Sat, 7 Jan 2012 15:50:08 +0100	[thread overview]
Message-ID: <20120107145008.GG25978@pengutronix.de> (raw)
In-Reply-To: <201201062336.31181.arnd@arndb.de>

On Fri, Jan 06, 2012 at 11:36:30PM +0000, Arnd Bergmann wrote:
> On Wednesday 04 January 2012, Russell King - ARM Linux wrote:
> > On Tue, Jan 03, 2012 at 10:43:06PM +0000, Arnd Bergmann wrote:
> > > The merge window is almost there, so it's time to look at what we've queued
> > > up in the arm-soc tree. There is a total of 55 branches with 386 non-merge
> > > changesets on top of mainline and the dependencies (linux-arm, v4l and
> > > dmaengine). The total diffstat is:
> > > 
> > >  676 files changed, 19694 insertions(+), 12633 deletions(-)
> > 
> > Well, my tree looks like this:
> >   937 files changed, 8150 insertions(+), 10774 deletions(-)
> >
> > > I would like to stop adding non-bugfix patches into the branches above now
> > > for 3.2, and instead merge everything that I receive from now on into
> > > late/* branches, so we don't destabilize the patches that are already there
> > > and so I can feel more comfortable about sending everything in the next/*
> > > branches upstream ASAP.
> > 
> > I think that's a must - for both our trees.  We have quite a number of
> > conflicts in linux-next between our trees and other trees - some of them
> > due to duplicated commits being applied.
> 
> Hmm, I'll have to check that, I was hoping that we manged to weed out
> the duplicated commits. Do you have a list, or some (semi-)automated
> way to find those, or are those just random commits you stumbled
> over.
You can look at

	git log --left-right --cherry-mark arm-soc...rmk ^linus/master | grep =

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

      reply	other threads:[~2012-01-07 14:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-03 22:43 Status of arm-soc.git for 3.2 Arnd Bergmann
2012-01-04 10:00 ` Russell King - ARM Linux
2012-01-04 18:17   ` ZenIV (was: Re: Status of arm-soc.git for 3.2) Russell King - ARM Linux
2012-01-04 18:55     ` Nicolas Pitre
2012-01-04 19:10       ` Russell King - ARM Linux
2012-01-04 20:04         ` Russell King - ARM Linux
2012-01-04 20:32           ` Nicolas Pitre
2012-01-06 23:36   ` Status of arm-soc.git for 3.2 Arnd Bergmann
2012-01-07 14:50     ` Uwe Kleine-König [this message]

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=20120107145008.GG25978@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).