All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: release-2010.12 branch ready for testing
Date: Fri, 19 Nov 2010 09:34:48 -0800	[thread overview]
Message-ID: <4CE6B538.6050801@balister.org> (raw)
In-Reply-To: <20101119144425.GC3411@jama>

On 11/19/2010 06:44 AM, Martin Jansa wrote:
....


> I think that short-lived branch is better, because every testing branch
> had few easy-to-fix issues which were fixed almost immediately in .dev
> after testing branched and it would be hard to choose which branch was best.
>
> But tag from any testing branch + first few quick fixes would be almost as
> good as based on any other testing branch.
>
> And I also agree with Phil that this short lived branch should be
> removed when the tag is created (to show that it's final state without
> maintainance).

I also think a *short lived* branch is a good route to try. I've been 
thinking about how the git history looks of a tag after you delete the 
branch leading up to it.

For emphasis, the short lived branch will not be used to maintain the tag.

Philip



  reply	other threads:[~2010-11-19 17:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 21:27 release-2010.12 branch ready for testing Khem Raj
2010-11-19  8:38 ` Frans Meulenbroeks
2010-11-19 10:34 ` Koen Kooi
2010-11-19 13:46   ` Tom Rini
2010-11-19 14:16     ` Koen Kooi
2010-11-19 14:44       ` Martin Jansa
2010-11-19 17:34         ` Philip Balister [this message]
2010-11-21  2:48           ` Khem Raj
2010-11-19 18:21       ` Khem Raj

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=4CE6B538.6050801@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-devel@lists.openembedded.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.