From: Jonathan Nieder <jrnieder@gmail.com>
To: Karel Zak <kzak@redhat.com>
Cc: Petr Uzel <petr.uzel@suse.cz>, util-linux@vger.kernel.org
Subject: Re: [PATCH] sfdisk: fix calculation due to type mismatch (ix86)
Date: Wed, 25 Apr 2012 10:16:03 -0500 [thread overview]
Message-ID: <20120425151603.GA31410@burratino> (raw)
In-Reply-To: <20120410103422.GJ19784@x2.net.home>
Hi Karel,
Karel Zak wrote:
> On Fri, Apr 06, 2012 at 04:53:13PM +0200, Petr Uzel wrote:
>> Addresses: https://bugzilla.novell.com/show_bug.cgi?id=754789
>> Reported-by: Dan Mares <dan.mares@norcrossgroup.com>
>> Signed-off-by: Petr Uzel <petr.uzel@suse.cz>
>
> Ah.. pretty dirty bug. Applied, thanks.
(This is 9c45d49fe01c "sfdisk: fix calculation due to type mismatch
(ix86)".) Thanks. Do you think this fix might belong in currently
maintained stable/ branches, too, and if so, how can I help make that
happen?
Context: http://bugs.debian.org/670127
Sincerely,
Jonathan
next prev parent reply other threads:[~2012-04-25 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 14:53 [PATCH] sfdisk: fix calculation due to type mismatch (ix86) Petr Uzel
2012-04-10 10:34 ` Karel Zak
2012-04-25 15:16 ` Jonathan Nieder [this message]
2012-05-02 7:22 ` Karel Zak
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=20120425151603.GA31410@burratino \
--to=jrnieder@gmail.com \
--cc=kzak@redhat.com \
--cc=petr.uzel@suse.cz \
--cc=util-linux@vger.kernel.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