Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit master 1/1] toolchain: do not require full path
Date: Fri, 22 Oct 2010 17:19:23 -0400	[thread overview]
Message-ID: <201010221719.23905.vapier@gentoo.org> (raw)
In-Reply-To: <871v7pet77.fsf@macbook.be.48ers.dk>

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.

what about branches ?  i dont see a problem with letting people 
create/maintain/push their own branches.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20101022/6f3b91f2/attachment.pgp>

  parent reply	other threads:[~2010-10-22 21:19 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 [this message]
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=201010221719.23905.vapier@gentoo.org \
    --to=vapier@gentoo.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