From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] RFC: package patching
Date: Thu, 17 Nov 2011 22:42:11 +0100 [thread overview]
Message-ID: <20111117224211.0e793a0b@skate> (raw)
In-Reply-To: <201111172123.05834.arnout@mind.be>
Le Thu, 17 Nov 2011 21:23:05 +0000,
Arnout Vandecappelle <arnout@mind.be> a ?crit :
> With that in mind, I would propose a format like this for backport
> patches:
>
> <pkg>-<seqno>-from_<nextversion>-description-of-the-patch
Having a comment inside a patch seems to be enough. Sometimes when the
patch is pushed upstream, it's merged in the Git repo of the upstream
project, but there isn't yet a release with the modification, so it
would be hard to known which "nextversion" the patch will be in.
We already have comments in patches, those comments can carry the
upstream status of the patch, which is also compatible with what we
intend to do with the send-patches.org project.
> I think ThomasP meant that it is best to _remove_ the version numbers.
> A version bumper will most likely try to take along all patches anyway, so
> putting a version number is just increasing the diffstat. Without version
> numbers, the diffstat will show much better which patches could be
> removed, which ones were added and which ones needed to be modified.
Agreed.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2011-11-17 21:42 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 [this message]
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
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=20111117224211.0e793a0b@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox