From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [pull request] Pull request for branch libusb-conversion
Date: Thu, 8 Apr 2010 12:30:53 +0200 [thread overview]
Message-ID: <20100408123053.3a04bc0b@surf> (raw)
In-Reply-To: <87y6gynuyh.fsf@macbook.be.48ers.dk>
On Thu, 08 Apr 2010 11:40:22 +0200
Peter Korsgaard <jacmet@uclibc.org> wrote:
> It's nice that you edited CHANGES for me, but this almost always causes
> merge conflicts, so I actually prefer to do it myself instead - OK?
Ok, makes sense.
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-04-08 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 19:56 [Buildroot] [pull request] Pull request for branch libusb-conversion Thomas Petazzoni
2010-04-06 19:56 ` [Buildroot] [PATCH 1/2] libusb: bump version, convert to autotools, add -compat lib Thomas Petazzoni
2010-04-06 19:56 ` [Buildroot] [PATCH 2/2] usb_modeswitch: use GENTARGETS instead of AUTOTARGETS Thomas Petazzoni
2010-04-08 9:40 ` [Buildroot] [pull request] Pull request for branch libusb-conversion Peter Korsgaard
2010-04-08 10: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=20100408123053.3a04bc0b@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