Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Makefile.autotools.in problems
Date: Thu, 10 Jul 2008 15:31:43 +0200	[thread overview]
Message-ID: <48760F3F.6030406@atmel.com> (raw)
In-Reply-To: <87y74aqiyy.fsf@macbook.be.48ers.dk>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Peter Korsgaard skrev:
>>>>>> "Daniel" == Daniel Laird <daniel.j.laird@nxp.com> writes:
> 
> Hi,
> 
>  Daniel> This is only a problem as I have not deleted patches
>  Daniel> associated with an old version.  However I wanted to raise
>  Daniel> the issue in case it was originally planned that you could
>  Daniel> have multiple patches in the directory for different versions
>  Daniel> and it would apply only those patches that match.
> 
> Yes, the Makefile.autotools.in is kinda half baked still.
> 
>  Daniel> Perhaps we could have a PKG_STRICT_PATCH variable.  That if
>  Daniel> set to true would only apply patches that match the version
>  Daniel> string, if not set it would apply all patches.
> 
> That or put the patches in version specific sub directories like
> openembedded does.
> 
I vote for the latter.

BR
ulf Samuelsson

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFIdg8/AyRRH5cXxqwRAmzjAJ4p57bU6fsdPWkpfyFHhzdTw587agCeIAkn
4JGH6fXyR/gHE24lpqg5kEM=
=EBnh
-----END PGP SIGNATURE-----

  reply	other threads:[~2008-07-10 13:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-10  7:37 [Buildroot] Makefile.autotools.in problems Daniel Laird
2008-07-10  7:47 ` Peter Korsgaard
2008-07-10 13:31   ` Ulf Samuelsson [this message]
2008-07-11  8:02     ` Daniel Laird
2008-07-11  8:17   ` Bernhard Fischer
2008-07-11  8:56     ` Daniel Laird
2008-07-11 12:36       ` Daniel Laird
2008-07-11 12:42         ` Daniel Laird

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=48760F3F.6030406@atmel.com \
    --to=ulf.samuelsson@atmel.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