From: Peter Williams <pwil3058@bigpond.net.au>
To: quilt-dev@nongnu.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Quilt-dev] Quilt 0.43 has been released! [SERIOUS BUG]
Date: Tue, 14 Feb 2006 14:25:30 +1100 [thread overview]
Message-ID: <43F14DAA.6000703@bigpond.net.au> (raw)
In-Reply-To: <20060202230210.05a6ad4a.khali@linux-fr.org>
Jean Delvare wrote:
> Hi all,
>
> Quilt 0.43 is now available for download from Savannah:
> http://download.savannah.gnu.org/releases/quilt/
>
> Enjoy!
>
I've experienced a serious problem with this version of quilt that is
rather hard to explain but definitely arrived with this version as
reverting to 0.42 makes the problem go away.
Now to try to explain the problem :-(
The problem arises when pushing a patch that has errors in it (due to
changes in the previous patches in the series) and needs the -f flag to
force the push. What's happening is that the reverse of the errors is
being applied to the "pre patch" file in the .pc directory. Then when
you pop this patch it returns the file to a state with the reverse of
the errors applied to it.
I'm having trouble understanding how quilt could be dumb enough to do
this as surely the "pre patch" file in the .pc directory should be just
a copy of the file before the patch is applied.
This bug can completely hose a set of patches if the user doesn't notice
it very early and do something about it. The work around is to revert
to version 0.42 of quilt.
Peter
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
next parent reply other threads:[~2006-02-14 3:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060202230210.05a6ad4a.khali@linux-fr.org>
2006-02-14 3:25 ` Peter Williams [this message]
2006-02-14 4:10 ` [Quilt-dev] Quilt 0.43 has been released! [SERIOUS BUG] Andreas Gruenbacher
2006-02-14 4:36 ` Peter Williams
2006-02-14 8:18 ` Jean Delvare
2006-02-14 15:15 ` Yasushi SHOJI
2006-02-14 15:55 ` Andreas Gruenbacher
2006-02-14 22:50 ` Peter Williams
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=43F14DAA.6000703@bigpond.net.au \
--to=pwil3058@bigpond.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=quilt-dev@nongnu.org \
/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