All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Williams <pwil3058@bigpond.net.au>
To: Jean Delvare <khali@linux-fr.org>
Cc: quilt-dev@nongnu.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Yasushi SHOJI <yashi@atmark-techno.com>
Subject: Re: [Quilt-dev] Quilt 0.43 has been released! [SERIOUS BUG]
Date: Wed, 15 Feb 2006 09:50:05 +1100	[thread overview]
Message-ID: <43F25E9D.6090702@bigpond.net.au> (raw)
In-Reply-To: <RyUOlVAg.1139905119.2584600.khali@localhost>

Jean Delvare wrote:
> Hi all,
> 
> On 2006-02-14, Andreas Gruenbacher wrote:
> 
>>On Tuesday 14 February 2006 04:25, Peter Williams wrote:
>>
>>>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.
>>
>>Found and fixed. It's a missed rollback_patch on one of the two branches of
>>the code that checks if a patch can be reverse applied. This case
>>apparently doesn't trigger as easily as it seems, or else we would have
>>found it sooner. Still quite bad.
> 
> 
> I probably encountered it the other day, but as I couldn't explain what
> was happening,  I mistakenly concluded to a user error and started again
> from a fresh tree. Or maybe it was really a user error after all.

I went through much the same process (several times) before it finally 
dawned on me that it might be a problem with the newly updated quilt and 
replaced it with 0.42 :-(.  I was worried that the symptoms were so 
bizarre and hard to describe properly that the problem would be hard to 
fix so I was impressed by the speed with which the problem was solved.

> 
> I was about to suggest that we add a test in the quilt test suite, but I
> see you did already - good!
> 
> 
>>Shall we wait until the translations are up-to-date again, or release
>>0.44 immediately?
> 
> 
> I'd say:
> * Fix the temporary file leak in the mail command I have been reporting a
> few days ago - unless it's there on purpose.
> * Update the translations. I'll take care of French this evening
> (GMT+01).
> * Let people (including me) do a little testing. If nothing else, running
> the test suite on a few different systems can't hurt.
> * Release.
> 
> We can be done by tomorrow if Yashi can handle the Japanese translation
> fast. If Yashi is too busy I guess we'll have to release anyway...

Peter
-- 
Peter Williams                                   pwil3058@bigpond.net.au

"Learning, n. The kind of ignorance distinguishing the studious."
  -- Ambrose Bierce

      parent reply	other threads:[~2006-02-14 22:50 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 ` [Quilt-dev] Quilt 0.43 has been released! [SERIOUS BUG] Peter Williams
2006-02-14  4:10   ` 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 [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=43F25E9D.6090702@bigpond.net.au \
    --to=pwil3058@bigpond.net.au \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quilt-dev@nongnu.org \
    --cc=yashi@atmark-techno.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 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.