Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] 2.6.33.2 kernel headers patch
Date: Wed, 07 Apr 2010 22:06:16 +0200	[thread overview]
Message-ID: <87zl1fownb.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <283831A4-C72C-440B-8959-4A1904239F54@me.com> (Thomas Brandstetter's message of "Wed, 07 Apr 2010 21:51:39 +0200")

>>>>> "Thomas" == Thomas Brandstetter <thomas.brandstetter@me.com> writes:

 Thomas> You're totally right, but I thought there is something wrong
 Thomas> with the mailing list because nobody wrote anything in reply
 Thomas> :-)

You can always check the archive if you're in doubt:

http://lists.busybox.net/pipermail/buildroot/

 Thomas> I'm not a developer and I'm not very familiar with git. Is
 Thomas> there a good documentation for Buildroot available how to send
 Thomas> git patches via the command line?

Buildroot is mainly a developer tool, but we do have documentation:

http://buildroot.net/buildroot.html
http://buildroot.net/git.html

The last has a link to the git homepage. There's very little buildroot
specific about how we use git, so a quick google search should find you
plenty of info (hint: we use the same approach like many other projects
like the Linux kernel, U-boot, ..).

The git commands you are looking for are:

git checkout -b <branch>
git commit
git format-patch -s master
git send-email --to buildroot at uclibc.org 0*.patch

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2010-04-07 20:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-03 12:39 [Buildroot] 2.6.33.2 kernel headers patch Thomas Brandstetter
2010-04-06 15:47 ` Thomas Brandstetter
2010-04-07  7:25   ` Peter Korsgaard
2010-04-07 19:51     ` Thomas Brandstetter
2010-04-07 20:06       ` Peter Korsgaard [this message]
2010-04-07  7:19 ` 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=87zl1fownb.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