Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] [git tag 2009.11] update for 2009.11
Date: Wed, 2 Dec 2009 07:01:50 -0600	[thread overview]
Message-ID: <200912020701.52887.minimod@morethan.org> (raw)
In-Reply-To: <20091201142204.3F954777B5@busybox.osuosl.org>

On Tue December 1 2009, Peter Korsgaard wrote:
> 
> commit: http://git.buildroot.net/buildroot/commit/?id=d0cb90792df5873af83f7277b17fe12aa1b91b19
> branch: http://git.buildroot.net/buildroot/commit/?id=refs/tags/2009.11
> 
> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
> 
> this is a tag, so no patch shown
>

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

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

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

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

Mike
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 
> 

  reply	other threads:[~2009-12-02 13:01 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 [this message]
2009-12-02 13:23   ` Peter Korsgaard
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=200912020701.52887.minimod@morethan.org \
    --to=minimod@morethan.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox