Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit:trunk/buildroot/target/device/Atmel/arch-avr32:kernel-patches-2.6.27.6
Date: Sat, 03 Jan 2009 08:58:31 +0100	[thread overview]
Message-ID: <87aba8253s.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <FC51A1FF4A8643D8A0C0B2C0DA0C5E2D@aeglos> (Ulf Samuelsson's message of "Fri\, 2 Jan 2009 23\:44\:37 +0100")

>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:

Hi,

 Ulf> The way it works now the patches are for a specific major/minor
 Ulf> combination but you select which kernel you want to use, and
 Ulf> then you select which patchset.  You can apply 2.6.27.6 on top
 Ulf> of 2.6.27.10 if you want to, but the name indicates which kernel
 Ulf> it was intended for, and the further away you go in terms of
 Ulf> major/minor revisions the higher the risk that the patch will
 Ulf> not apply.

But why are you checking in something that is already obsolete? Why
not base on 2.6.27.10 right away?

 Ulf> When I get time, I will implement downloading the patchset
 Ulf> instead of storing it in the svn.
 Ulf> Then the size will go down.

And what about the older patches, can they go away?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2009-01-03  7:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-20 22:19 [Buildroot] svn commit: trunk/buildroot/target/device/Atmel/arch-avr32: kernel-patches-2.6.27.6 ulf at uclibc.org
2008-12-23  9:48 ` Peter Korsgaard
2009-01-02 22:44   ` [Buildroot] svn commit:trunk/buildroot/target/device/Atmel/arch-avr32:kernel-patches-2.6.27.6 Ulf Samuelsson
2009-01-03  7:58     ` Peter Korsgaard [this message]
2009-01-03  9:33       ` Ulf Samuelsson

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=87aba8253s.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