All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [ANNOUNCE] Fine grained branches
Date: Thu, 04 Apr 2013 11:18:08 +0000	[thread overview]
Message-ID: <1908922.cTRUnWqvNx@avalon> (raw)
In-Reply-To: <20130404070700.GA10022@verge.net.au>

Hi Simon,

On Thursday 04 April 2013 16:07:00 Simon Horman wrote:
> Hi,
> 
> in an effort to streamline management of the renesas tree I am trying the
> use of more fine-grained branches.
> 
> For the past few release there have been the following branches:
> 
> * defconfig
> * boards
> * soc
> * pinmux
> 
> Some sundry branches for drivers. And merge branches that bring things
> together. Currently next is the only merge branch I am maintaining.
> 
> Going forwards I plan to make per-board defconfig and boards branches and
> per-soc pinmux and soc branches.

I wonder whether it might not be too soon for per-SoC pinmux branches. I will 
still need to perform cross-SoC changes to the PFC driver for v3.11 to 
implement DT support. Splitting the patches in per-SoC pinmux branches 
wouldn't be practical, as there would likely be many cross-dependencies. The 
situation should hopefully stabilize after v3.11.

> So instead of applying an sh73a0 patch to soc, I will apply it to soc-
> sh73a0.
> 
> I will, as before, merge all relevant branches into next.
> 
> I have also recently starting taging next branches, to provide a reference
> point for developers. Unlike next, which changes every time I do a merge of
> new changes, tags don't change (unless I make a mistake!). The current tag
> is renesas-next-20130303. I plan to make renesas-next-20130304 shortly.
> Please consider basing your work on the latest renesas-next tag. And please
> consider quoting the tag name your work is based on when posting it.

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2013-04-04 11:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04  7:07 [ANNOUNCE] Fine grained branches Simon Horman
2013-04-04 11:18 ` Laurent Pinchart [this message]
2013-04-05  0:26 ` Simon Horman

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=1908922.cTRUnWqvNx@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-sh@vger.kernel.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 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.