Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] X11 component versions
Date: Mon, 18 Mar 2013 09:05:02 +0100	[thread overview]
Message-ID: <5146CAAE.5060508@mind.be> (raw)
In-Reply-To: <CALnvph2VjwKv6U38KpR3JtWozs_zPWDzpu5stGpREuJHcdGw0Q@mail.gmail.com>

  Hi Jesper,

On 03/12/13 09:52, Jesper Birks? B?kdahl wrote:
[snip]
> I have tried to rebase the x11r7.7 patches on master. I chose not to
> remove all app components for the reasons mentioned by Nicolas Dechesne.
>
> As this is my first time contributing to buildroot, I don't know the
> procedures when dealing with this many patches at once, so for now I have
> just pushed my version of the branch to:
> https://bitbucket.org/baekdahl/buildroot/src/b8db03aa6921/?at=x11r77

  Thank you for your work. Clearly, nobody has taken a look yet :-). It 
is probably better to post the patch series to the list after all. You 
will most likely only get feedback on the first few patches, but there's 
no problem with that, right? Posting a long patch series only has the 
disadvantage of a bit more patchwork cleanup work.

  Here are some pointers about what we like to see in patches:

- Use git send-email to send them.

- Make sure all of them are Signed-off-by you, even if you didn't author 
them (just put your Sob under the original author's; cfr. Peter's Sob's 
in the git log).

- In patches which have been submitted before, add a changelog (under the 
Sob lines, separated by ---).

- Add an introductory e-mail (with git send-email --compose) explaining 
what the series is about, and indicating which parts you're less sure of 
and would like to get feedback on.


  Regards,
  Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2013-03-18  8:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12  8:52 [Buildroot] X11 component versions Jesper Birksø Bækdahl
2013-03-18  8:05 ` Arnout Vandecappelle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-02-04  9:44 Nicolas Dechesne
2013-02-04 10:45 ` Will Wagner
2013-02-04 10:56   ` Nicolas Dechesne
2013-02-04 11:11     ` Will Wagner
2013-02-04 20:40       ` Thomas Petazzoni
2013-02-04 20:49         ` Nicolas Dechesne
2013-02-04 21:30           ` Thomas Petazzoni
2013-02-04 21:37             ` Nicolas Dechesne
2013-02-04 22:06               ` Arnout Vandecappelle
2013-02-04 22:41                 ` Nicolas Dechesne
2013-02-04 22:24               ` Thomas Petazzoni
2013-02-04 22:45                 ` Nicolas Dechesne
2013-02-04 22:54                   ` Thomas Petazzoni
2013-02-04 20:42       ` Nicolas Dechesne
2013-02-04 22:46 ` 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=5146CAAE.5060508@mind.be \
    --to=arnout@mind.be \
    --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