From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit master 1/1] toolchain: do not require full path
Date: Sun, 17 Oct 2010 13:37:57 +0200 [thread overview]
Message-ID: <87wrphcane.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <201010161810.44330.vapier@gentoo.org> (Mike Frysinger's message of "Sat, 16 Oct 2010 18:10:43 -0400")
>>>>> "Mike" == Mike Frysinger <vapier@gentoo.org> writes:
Hi,
Mike> On Saturday, October 16, 2010 17:14:20 Peter Korsgaard wrote:
>> Thanks, but please don't commit to the buildroot tree directly. We use a
>> setup like the kernel, so send patches/pull requests like everyone else.
Mike> np. there didnt seem to be any developer documentation that
Mike> explained this, nor did people comment on my patches.
I'm doing my best, but I know there's quite a backlog at the moment. If
you follow the list you will see me commenting on patching and
committing several times a week though.
Regarding documentation, http://buildroot.net/git.html does state:
Because you've only been granted anonymous access to the tree, you won't
be able to commit any changes. Changes can be submitted for inclusion by
posting them to the buildroot mailing list or to the Bug and Patch
Tracking System.
Which I agree could be clearer.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2010-10-17 11:37 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 [this message]
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
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=87wrphcane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox