mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Thierry Vignaud <tvignaud@mandriva.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	util-linux-ng@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux-ng v2.14.1 (stable)
Date: Wed, 10 Sep 2008 16:26:05 +0200	[thread overview]
Message-ID: <20080910142605.GA6092@nb.net.home> (raw)
In-Reply-To: <m24p4op2gm.fsf@vador.mandriva.com>

On Wed, Sep 10, 2008 at 03:14:49PM +0200, Thierry Vignaud wrote:
> Err, since you're both:
> - the official upstream author,
> - the official packager in fedora,
> 
> why do you package so many uncommited patches in your fedora package?

> util-linux-ng-2.13-ctrlaltdel-man.patch

 distribution specific patch

> util-linux-ng-2.13-fdformat-man-ide.patch
> util-linux-ng-2.13-floppy-generic.patch
> util-linux-ng-2.13-floppy-locale.patch

 distribution specific patches -- upstream does not include
 the"floppy" util

> util-linux-ng-2.13-fdisk-b-4096.patch
> util-linux-ng-2.13-ipcs-32bit.patch
> util-linux-ng-2.13-login-lastlog.patch
> util-linux-ng-2.13-login-pamstart.patch

 not sure, maybe good enough for upstream (we will see in 2.15..)

> util-linux-ng-2.13-mount-pamconsole.patch

 old distribution specific patch (not planned for F10)

> util-linux-ng-2.14-blockdev-rmpart.patch

 (stupid) distribution specific patch (duplicate delpart(1)
 functionality.

> util-linux-ng-2.14-mount-file_t.patch

 already in upstream devel repository

> util-linux-ng-2.14-mount-managed.patch

 distribution specific patch


    Karel

-- 
 Karel Zak  <kzak@redhat.com>

      reply	other threads:[~2008-09-10 14:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-10 12:40 Karel Zak
2008-09-10 13:14 ` Thierry Vignaud
2008-09-10 14:26   ` Karel Zak [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=20080910142605.GA6092@nb.net.home \
    --to=kzak@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tvignaud@mandriva.com \
    --cc=util-linux-ng@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

all inboxes | Powered by JetHome®