All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] RFC: package patching
Date: Fri, 18 Nov 2011 17:41:12 +0100	[thread overview]
Message-ID: <20111118174112.08e536cd@skate> (raw)
In-Reply-To: <CAAXf6LW_qTUwtbdC+QjYnUAd1w5gZ4H55-6+G1Gnt3NV-s4F5w@mail.gmail.com>

Le Thu, 17 Nov 2011 14:05:47 +0100,
Thomas De Schampheleire <patrickdepinguin+buildroot@gmail.com> a ?crit :

> Although you are right that there is no such thing as a generic patch,
> I still feel there is a conceptual difference between:
> * modifications intended for all versions of a package, for example
> modifications that we know will never go upstream because they are
> buildroot-specific, and
> * modifications which are intended for a specific version, for example
> a backport of a change that was already fixed in a later version.

I get your point.

> To remove our reliance on 'luck', I agree it may be best to add
> version numbers to either type of patch. If a package has multiple
> versions, the patch may simply be duplicated with separate version
> numbers.
> 
> But, should we mark the difference between such patches in a
> different way?

Yes, through comments in the respective patch descriptions.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      parent reply	other threads:[~2011-11-18 16:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-15  8:33 [Buildroot] RFC: package patching Thomas De Schampheleire
2011-11-15  8:45 ` Peter Korsgaard
2011-11-15 19:14   ` Arnout Vandecappelle
2011-11-15 21:28     ` Thomas Petazzoni
2011-11-16  6:18       ` Sergey Naumov
2011-11-16  6:50         ` Thomas De Schampheleire
2011-11-16  6:44       ` Thomas De Schampheleire
2011-11-16 18:03         ` Thomas Petazzoni
2011-11-17 13:05           ` Thomas De Schampheleire
2011-11-17 21:23             ` Arnout Vandecappelle
2011-11-17 21:42               ` Thomas Petazzoni
2011-11-18  6:53                 ` Thomas De Schampheleire
2011-11-18  7:05                   ` Thomas Petazzoni
2011-11-18  7:34                     ` Peter Korsgaard
2011-11-18  9:26                       ` Thomas De Schampheleire
2011-11-18 12:24                   ` Michael S. Zick
2011-11-18 19:44                   ` Arnout Vandecappelle
2011-11-18 19:27                 ` Arnout Vandecappelle
2011-11-19  9:26                   ` Bjørn Forsman
2011-11-19 12:13                     ` Arnout Vandecappelle
2011-11-18 16:41             ` Thomas Petazzoni [this message]

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=20111118174112.08e536cd@skate \
    --to=thomas.petazzoni@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.