From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PULL] u-boot-socfpga/topic/arm/socfpga-20141010
Date: Sat, 11 Oct 2014 21:22:57 +0200 [thread overview]
Message-ID: <201410112122.57450.marex@denx.de> (raw)
In-Reply-To: <E1Xcjjz-0005FB-05@janus>
On Saturday, October 11, 2014 at 01:36:53 AM, Albert ARIBAUD wrote:
> Hi Marek,
Hi Albert,
> On Sat, 11 Oct 2014 01:11:46 +0200, Marek Vasut <marex@denx.de> wrote:
> > The following changes since commit db67801bf92f7fae6131dbc0d387131698fb9490:
> > Merge branch 'master' of git://git.denx.de/u-boot-nand-flash
> > (2014-10-10
> >
> > 09:45:16 -0400)
> >
> > are available in the git repository at:
> > git://git.denx.de/u-boot-socfpga.git topic/arm/socfpga-20141010
>
> In the U-Boot process, PRs are done from a master branch to a master
> branch.
>
> There are exceptions of course, for instance when a repo collects
> patches for more than one architecture, as does u-boot-sh; it has a
> master branch for its SH stuff, and a 'rmobile' branch for its ARM
> stuff.
>
> But here, the branch is topical. This is very unusual and only
> happened, AFAIR, in very few cases of big changes across all arches,
> where by agreement the patch series was directly maintained as a branch.
>
> Will u-boot-socfpga keep on using this branch system, or will it in the
> future converge toward the U-Boot master+next branch system?
Yes, the next MW will be taking the standard course through master+next combo.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-10-11 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 23:11 [U-Boot] [PULL] u-boot-socfpga/topic/arm/socfpga-20141010 Marek Vasut
2014-10-10 23:36 ` Albert ARIBAUD
2014-10-11 19:22 ` Marek Vasut [this message]
2014-10-11 8:22 ` Albert ARIBAUD
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=201410112122.57450.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.de \
/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