Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Heidelberg <markus.heidelberg@web.de>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/hotplug
Date: Wed, 17 Dec 2008 10:51:12 +0100	[thread overview]
Message-ID: <200812171051.12956.markus.heidelberg@web.de> (raw)
In-Reply-To: <9305ca410812170140r1bf63f0ereb8ad96246740e7b@mail.gmail.com>

Peter Korsgaard, 17.12.2008:
> On Wed, Dec 17, 2008 at 7:32 AM,  <hamish@uclibc.org> wrote:
> > Author: hamish
> > Date: 2008-12-16 22:32:19 -0800 (Tue, 16 Dec 2008)
> > New Revision: 24436
> >
> > Log:
> > Revert $(strip ...) change which corrupted this file
> 
> Argh, sorry about that - Seems like sed went a bit over board :/

These files are also affected:

   trunk/buildroot/package/openswan/linux-2.6.20-openswan-2.4.7.kernel-2.6-klips.patch
   trunk/buildroot/package/openswan/linux-2.6.20.4-openswan-2.4.7.kernel-2.6-klips.patch
   trunk/buildroot/package/openswan/linux-2.6.21.5-openswan-2.4.8.kernel-2.6-klips.patch
   trunk/buildroot/package/openswan/linux-2.6.22.6-openswan-2.4.9.kernel-2.6-klips.patch

And it seems that the openswan directory contains several outdated
patches.

Markus

  reply	other threads:[~2008-12-17  9:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-17  6:32 [Buildroot] svn commit: trunk/buildroot/package/hotplug hamish at uclibc.org
2008-12-17  9:40 ` Peter Korsgaard
2008-12-17  9:51   ` Markus Heidelberg [this message]
2008-12-17 10:31     ` Peter Korsgaard
  -- strict thread matches above, loose matches on Subject: below --
2007-10-18 22:59 ulf at uclibc.org
2006-08-10 20:08 andersen at uclibc.org
2006-08-11  5:01 ` Ulf Samuelsson
2006-08-14 16:45   ` Erik Andersen
2006-08-14 21:22     ` Ulf Samuelsson
2006-08-15 21:31       ` Rob Landley
2006-08-16 18:23       ` Erik Andersen

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=200812171051.12956.markus.heidelberg@web.de \
    --to=markus.heidelberg@web.de \
    --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