From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot git usage model
Date: Fri, 12 Oct 2012 07:29:48 +0200 [thread overview]
Message-ID: <5077AACC.6000403@denx.de> (raw)
In-Reply-To: <1349980244.6903.13@snotra>
On 10/11/2012 08:30 PM, Scott Wood wrote:
>> But, yes, it bears more thinking if we want the next branch open for
>> longer than it has historically been, if we want that. And we have at
>> least historically been saying that next can and will be rebased.
>
> IMHO it would be nice for the next branch to open immediately after the
> merge window closes, and be kept up to date except during the merge
> window. Historically the next branch has opened when someone requests
> a pull into it, but how do I make a sane pull request when the next
> branch has been untouched since the last release?
This has been discussed on the U-Boot BoF in Geneva a few months ago.
And it was generally agreed upon that opening the next branch earlier
(best directly after the merge window) would be a big plus.
IIRC, then Tom did exactly this in this release cycle.
Thanks,
Stefan
next prev parent reply other threads:[~2012-10-12 5:29 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-07 18:49 [U-Boot] [PULL] u-boot-usb/next Marek Vasut
2012-10-09 14:23 ` Tom Rini
2012-10-09 21:03 ` [U-Boot] U-Boot git usage model (was: Re: [PULL] u-boot-usb/next) Stephen Warren
2012-10-09 21:32 ` Tom Rini
2012-10-09 22:14 ` [U-Boot] U-Boot git usage model Stephen Warren
2012-10-09 22:43 ` Albert ARIBAUD
2012-10-09 23:02 ` Graeme Russ
2012-10-09 22:59 ` Tom Rini
2012-10-09 23:07 ` Stephen Warren
2012-10-09 23:17 ` Graeme Russ
2012-10-09 23:00 ` Scott Wood
2012-10-09 23:25 ` Stephen Warren
2012-10-10 0:20 ` Scott Wood
2012-10-10 15:55 ` Stephen Warren
2012-10-10 22:02 ` Scott Wood
2012-10-10 22:19 ` Stephen Warren
2012-10-11 7:19 ` Wolfgang Denk
2012-10-11 11:53 ` Jason Cooper
2012-10-11 17:00 ` Stephen Warren
2012-10-13 19:08 ` Wolfgang Denk
2012-10-11 16:27 ` Albert ARIBAUD
2012-10-11 7:28 ` Wolfgang Denk
2012-10-11 16:54 ` Stephen Warren
2012-10-13 18:58 ` Wolfgang Denk
2012-10-09 22:19 ` [U-Boot] U-Boot git usage model (was: Re: [PULL] u-boot-usb/next) Albert ARIBAUD
2012-10-09 23:04 ` [U-Boot] U-Boot git usage model Stephen Warren
2012-10-10 6:15 ` Albert ARIBAUD
2012-10-10 16:04 ` Stephen Warren
2012-10-10 18:40 ` Albert ARIBAUD
2012-10-11 16:54 ` Scott Wood
2012-10-11 17:16 ` Albert ARIBAUD
2012-10-11 17:26 ` Stephen Warren
2012-10-11 18:30 ` Albert ARIBAUD
2012-10-13 19:30 ` Wolfgang Denk
2012-10-13 21:13 ` Tom Rini
2012-10-13 22:25 ` Wolfgang Denk
2012-10-15 17:56 ` Tom Rini
2012-10-15 19:00 ` Wolfgang Denk
2012-10-13 19:17 ` Wolfgang Denk
2012-10-15 16:32 ` Stephen Warren
2012-10-15 18:55 ` Wolfgang Denk
2012-10-15 21:42 ` Stephen Warren
2012-10-11 18:13 ` Scott Wood
2012-10-11 18:45 ` Albert ARIBAUD
2012-10-11 18:59 ` Scott Wood
2012-10-12 10:11 ` Albert ARIBAUD
2012-10-12 21:49 ` Scott Wood
2012-10-13 19:20 ` Wolfgang Denk
2012-10-13 19:06 ` Wolfgang Denk
2012-10-11 7:17 ` Wolfgang Denk
2012-10-11 16:38 ` [U-Boot] U-Boot git usage model (was: Re: [PULL] u-boot-usb/next) Tom Rini
2012-10-11 17:16 ` Scott Wood
2012-10-11 17:22 ` [U-Boot] U-Boot git usage model Stephen Warren
2012-10-11 17:27 ` Tom Rini
2012-10-11 18:30 ` Scott Wood
2012-10-12 5:29 ` Stefan Roese [this message]
2012-10-12 15:49 ` Tom Rini
2012-10-13 19:34 ` Wolfgang Denk
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=5077AACC.6000403@denx.de \
--to=sr@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 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.