From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Henning Schild" <henning.schild@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] Merge patch and unpack tasks
Date: Mon, 25 Feb 2019 11:01:28 +0100 [thread overview]
Message-ID: <38dfdff5-61e7-5ee6-85f6-3a9042edd29c@siemens.com> (raw)
In-Reply-To: <20190225104759.48a8c7ad@md1za8fc.ad001.siemens.net>
On 25.02.19 10:47, [ext] Henning Schild wrote:
> That is a well known problem. You will have to clean again or somehow
> bump the version of the package. During development manual cleaning is
> OK,
No, it's not.
> for new releases you commit a version bump should be done anyway
> when changing the sources.
>
> I guess the merge does not cover patching sources unpacked with
> "apt-get source", you will run into the same issue here.
Good point: The apt unpacking happens in a different, I bet. Hmm, then we
probably need to make patching truly reversible.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-02-25 10:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 10:44 Jan Kiszka
2019-02-25 9:47 ` Henning Schild
2019-02-25 10:01 ` Jan Kiszka [this message]
2019-03-04 8:51 ` Claudius Heine
2019-03-04 9:11 ` Jan Kiszka
2019-03-08 15:58 ` cedric_hombourger
2019-03-08 16:34 ` Jan Kiszka
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=38dfdff5-61e7-5ee6-85f6-3a9042edd29c@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
/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