All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] target-finalize: fix libthread_db strip fix
Date: Mon, 29 Nov 2010 22:14:47 +0100	[thread overview]
Message-ID: <87eia3ygqg.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <201011291544.27824.vapier@gentoo.org> (Mike Frysinger's message of "Mon, 29 Nov 2010 15:44:26 -0500")

>>>>> "Mike" == Mike Frysinger <vapier@gentoo.org> writes:

 Mike> On Monday, November 29, 2010 06:41:40 Peter Korsgaard wrote:
 >> >>>>> "Mike" == Mike Frysinger <vapier@gentoo.org> writes:
 Mike> which would be nice to know ... from my point of view, these are
 Mike> simply being ignored with no feedback.  but perhaps this gets
 Mike> back to the buildroot doc not really covering any dev/release
 Mike> processes yet.
 >> 
 >> True. We follow the same general structure as a bunch of other projects
 >> (E.G. Linux, u-boot, barebox, ..).

 Mike> by "structure", i'm guessing you mean "release/development process" ?

Yes. There's naturally some scale differences, but we follow the general
process:

- Releases every 3 months
- Only the maintainer (me) has direct commit access
- A period (2 months) after a release the tree is open for new features,
  then -rc1 is released and only fixes are accepted.
- We use similar commit msg structure and signed-off-by / acked-by's

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2010-11-29 21:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-27 22:43 [Buildroot] [PATCH] target-finalize: fix libthread_db strip fix Mike Frysinger
2010-11-28 10:09 ` Peter Korsgaard
2010-11-28 17:36   ` Mike Frysinger
2010-11-28 21:14     ` Peter Korsgaard
2010-11-28 22:13       ` Mike Frysinger
2010-11-29  7:53         ` Peter Korsgaard
2010-11-29 11:21           ` Mike Frysinger
2010-11-29 11:41             ` Peter Korsgaard
2010-11-29 20:44               ` Mike Frysinger
2010-11-29 21:14                 ` Peter Korsgaard [this message]
2010-11-29 23:45                   ` Mike Frysinger
2010-11-28 22:25       ` Mike Frysinger
2010-11-29  7:57         ` Peter Korsgaard
2010-11-29 11:18           ` Mike Frysinger
2010-11-29 11:38             ` Peter Korsgaard

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=87eia3ygqg.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.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 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.