From: Andreas Pretzsch <apr@cn-eng.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] ptxdist migrate should check for local patches in case of package version change
Date: Sat, 24 May 2014 19:10:20 +0200 [thread overview]
Message-ID: <1400951420.8697.41.camel@ws-apr.office.loc> (raw)
Scenario: There are local patches against a package in "patches" or
"config/<platform>/patches", which are for one or another legit reason
not (yet) upstream.
Now, when updating to a newer ptxdist version, it is possible that the
version number of such a package changed. Which in turn means that the
local patches are no longer used. Something that can go unnoticed for
quite some time, until the reason for these local patches were added
initially hit.
Just happened here...
Suggestion: Have "ptxdist migrate" check for this situation and issue a
warning.
As I'll be missing the time to look into this for the foreseeable
future, I just throw it in here as an addition to the famous TODO
list ;-)
--
carpe noctem engineering
Ingenieurbuero fuer Hard- & Software-Entwicklung Andreas Pretzsch
Dipl.-Ing. (FH) Andreas Pretzsch Tel. +49-(0)731-5521572
Hahnengasse 3 Fax: +49-(0)731-5521571
89073 Ulm, Germany email: apr@cn-eng.de
--
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2014-05-24 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-24 17:10 Andreas Pretzsch [this message]
2014-05-24 18:02 ` Robert Schwebel
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=1400951420.8697.41.camel@ws-apr.office.loc \
--to=apr@cn-eng.de \
--cc=ptxdist@pengutronix.de \
/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