All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@sunsite.dk>
To: buildroot@busybox.net
Subject: [Buildroot] [git tag 2009.11] update for 2009.11
Date: Wed, 02 Dec 2009 14:23:26 +0100	[thread overview]
Message-ID: <873a3tv7ap.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <200912020701.52887.minimod@morethan.org> (Michael S. Zick's message of "Wed, 2 Dec 2009 07:01:50 -0600")

>>>>> "Michael" == Michael S Zick <minimod@morethan.org> writes:

 Michael> Would you please tag the repository with a 2010.02 branch tag?

Sorry, I prefer to branch for bugfix releases instead (if needed) - So
that master is always where development is happening.

 Michael> That way users can continue to fix 2009.11 without being exposed
 Michael> to the code-churn of producing 2010.02.

Just create a local branch from the 2009.11 tag:

git checkout -b mybranch 2009.11

 Michael> The "release and move-on" type of organization really is not appropriate
 Michael> for something as mission critical as the build system in use.

 Michael> Heck, after a decade, even kernel.org learned that lesson.  ;)

No they didn't. Linus' tree doesn't have branches, and stable (bugfix)
releases are done from a completely different tree.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-12-02 13:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-01 14:20 [Buildroot] [git tag 2009.11] update for 2009.11 Peter Korsgaard
2009-12-02 13:01 ` Michael S. Zick
2009-12-02 13:23   ` Peter Korsgaard [this message]
2009-12-02 13:37     ` Michael S. Zick
2009-12-02 13:48       ` Peter Korsgaard
2009-12-02 14:18         ` Michael S. Zick

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=873a3tv7ap.fsf@macbook.be.48ers.dk \
    --to=jacmet@sunsite.dk \
    --cc=buildroot@busybox.net \
    /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.