Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Enable i830 graphics driver for DirectFB
Date: Wed, 23 Sep 2009 09:24:52 +0200	[thread overview]
Message-ID: <87tyyurum3.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1253682420.451.64.camel@station1.ormlab.com> (Ormund Williams's message of "Wed\, 23 Sep 2009 01\:06\:59 -0400")

>>>>> "Ormund" == Ormund Williams <ormundw@panix.com> writes:

 Ormund> I'm still learning to use git, so if anyone can turn these diffs into a
 Ormund> real patch I would appreciate it.

Normally you would simply commit changes locally on another branch, run
git format-patch master and then (preferably) send them with git-email or
through your normal mail program.

E.G. git checkout -b something
git commit -a
git format-patch master
git send-email --to buildroot at uclibc.org 0*.patch
git checkout master
rm 0*patch

Could you give it a try?

-- 
Bye, Peter Korsgaard

      reply	other threads:[~2009-09-23  7:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-23  5:06 [Buildroot] Enable i830 graphics driver for DirectFB Ormund Williams
2009-09-23  7:24 ` Peter Korsgaard [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=87tyyurum3.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