From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit master 1/1] toolchain: do not require full path
Date: Sat, 23 Oct 2010 13:30:56 +0200 [thread overview]
Message-ID: <20101023133056.24a6d6fe@surf> (raw)
In-Reply-To: <AANLkTinktTTjKWoJSy16bka6o7Q1dim2O6Fy8_AFEm6j@mail.gmail.com>
Hello,
On Sat, 23 Oct 2010 04:32:58 -0400
Mike Frysinger <vapier@gentoo.org> wrote:
> not really. there are plenty of examples where people are allowed to
> maintain their own branch in the same "master" tree. uClibc, glibc,
> OE off the top of my head.
I personally don't see any big advantage of this option compared to the
current organization and workflow, it seems just to be a matter of
personal taste. So let's keep the workflow we've been using for the
last two years, which has proven to be pretty good for Buildroot
development.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2010-10-23 11:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-16 20:46 [Buildroot] [git commit master 1/1] toolchain: do not require full path Mike Frysinger
2010-10-16 21:14 ` Peter Korsgaard
2010-10-16 22:10 ` Mike Frysinger
2010-10-17 11:37 ` Peter Korsgaard
2010-10-17 22:34 ` Mike Frysinger
2010-10-18 7:10 ` Peter Korsgaard
2010-10-22 21:19 ` Mike Frysinger
2010-10-23 0:53 ` Thomas Petazzoni
2010-10-23 6:47 ` Peter Korsgaard
2010-10-23 8:32 ` Mike Frysinger
2010-10-23 8:46 ` Peter Korsgaard
2010-10-23 11:30 ` Thomas Petazzoni [this message]
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=20101023133056.24a6d6fe@surf \
--to=thomas.petazzoni@free-electrons.com \
--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