Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thiago A. Corrêa" <thiago.correa@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [GIT PULL] avr32 updates
Date: Fri, 8 May 2009 04:59:37 -0300	[thread overview]
Message-ID: <d6cda7730905080059o7fa58ba6w3bf66241b0c90bc2@mail.gmail.com> (raw)
In-Reply-To: <877i0scbjf.fsf@macbook.be.48ers.dk>

Hi,

On Fri, May 8, 2009 at 4:13 AM, Peter Korsgaard <jacmet@uclibc.org> wrote:
>>>>>> "Thiago" == Thiago A Corr?a <thiago.correa@gmail.com> writes:
>
> ?Thiago> Hi Peter,
> ?Thiago> ? ? I'm newbie with this git thing, so please bear with me...
>
> ?Thiago> ? ? Please pull git clone git://git.buildroot.net/~correa/git/buildroot.git for:
>
> ?Thiago> ?* Update Linux Advanced to 2.6.29.2 - this fixes iptables compile
> ?Thiago> ?* Add dl folder to gitignore
> ?Thiago> ?* Update atngw100_defconfig
>
> I had a quick look, and it basically looks good, but there's a few
> things I would like you to fix:
>
> - Please sign off on your fixes (git commit -s)

Can this be done easily after it has been commited? Since I had setup
my name and address, I had hopes that it would do it automagically.

> - Don't commit unrelated things together (Linux advanced together with
> ?atngw100 defconfig)

Ok.

> - What do you mean with 'this fixes iptables compile'? What does the
> ?kernel has to do with iptables compilation?

Something is wrong in the kernel headers in previous versions.
Something in byteorder.h prevended it from building earlier.

> You are welcome to put the fixes for 2009.05 in a seperate branch
> (upstream, stable or whatever) if that's easier for you to keep it
> seperate for new feature development while we're stabilizing for the
> release. I might create a 'next' branch for new stuff.
>

I thought of using master for current and 2009.07 for next. But I
could use a suggestion anyway.

About the .gitignore, I didn't base it from a patch, I actually added
it myself because git was always complaining about it and I had to do
git commit -m "" -a
But feel free to apply a previous patch that does the same. I still
haven't figured out how to do git am stuff :D

Btw, how does one get those nice summaries like this ?
http://lkml.org/lkml/2009/4/4/40


Kind Regards,
   Thiago A. Correa

  reply	other threads:[~2009-05-08  7:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-08  4:52 [Buildroot] [GIT PULL] avr32 updates Thiago A. Corrêa
2009-05-08  7:13 ` Peter Korsgaard
2009-05-08  7:59   ` Thiago A. Corrêa [this message]
2009-05-08  8:29     ` Peter Korsgaard
2009-05-08  9:17       ` Thiago A. Corrêa
2009-05-08  9:48         ` Peter Korsgaard
2009-05-08  9:57           ` Peter Korsgaard
2009-05-08 10:30             ` Peter Korsgaard
2009-05-08 10:56           ` Thiago A. Corrêa
2009-05-08 11:03             ` Daniel Mack
2009-05-08 16:59             ` Thiago A. Corrêa
2009-05-08 17:06               ` Peter Korsgaard
2009-05-09  9:18             ` Markus Heidelberg
2009-05-09  8:50           ` Markus Heidelberg
2009-05-12 10:30             ` Peter Korsgaard
2009-05-12 17:33               ` Thiago A. Corrêa
2009-05-12 19:46                 ` Peter Korsgaard
2009-05-12 20:09                   ` Thiago A. Corrêa
2009-05-12 20:27                     ` Peter Korsgaard
2009-05-08  7:15 ` Peter Korsgaard
2009-05-08  8:25 ` Daniel Mack

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=d6cda7730905080059o7fa58ba6w3bf66241b0c90bc2@mail.gmail.com \
    --to=thiago.correa@gmail.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