Util-Linux package development
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: David Brownell <david-b@pacbell.net>
Cc: List util-linux-ng <util-linux-ng@vger.kernel.org>
Subject: Re: what happend with hwclock patches?
Date: Wed, 7 Mar 2007 11:42:57 +0100	[thread overview]
Message-ID: <20070307104257.GC25806@petra.dvoda.cz> (raw)
In-Reply-To: <200703062006.27793.david-b@pacbell.net>

On Tue, Mar 06, 2007 at 08:06:27PM -0800, David Brownell wrote:
> See
>   http://bugzilla.kernel.org/show_bug.cgi?id=8138

 Thanks for this link. The patch is not applied yet. Maybe I should
 release a snapshot (at least) with urgent things like hwclock or some
 mount patches.

 But I think you should ask downstream (your distribution) maitainer
 to apply these kind of patches. They have pretty stable util-linux
 packages now. I'll need few weeks to prepare useful util-linux-ng release.

 (I'm going to add the patch to Fedora tree.)

> I see there's a GIT archive but you don't seem to have merged the patch I sent
> you back in November ... and the GIT tree doesn't show any active development,
> no commits except syncing to old releases.

 Please, don't use broken gitweb at kernel.org or use it very carefully.

 There is active development, see "log" in the devel branch:

   http://git.kernel.org/?p=utils/util-linux-ng/util-linux-ng.git;a=log;h=devel

 Number of applied patches:

    $ git rev-list --pretty=oneline  devel ^master | wc -l
    52

 Number of patches in queue:

    $ ls util-* | wc -l
    49

 The good news is that I have more time and I work on that full time
 now.

        Karel

-- 
 Karel Zak  <kzak@redhat.com>

       reply	other threads:[~2007-03-07 10:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200703062006.27793.david-b@pacbell.net>
2007-03-07 10:42 ` Karel Zak [this message]
2007-03-07 17:42   ` what happend with hwclock patches? David Brownell
2007-03-07 19:01     ` Karel Zak
2007-03-07 20:08       ` David Brownell

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=20070307104257.GC25806@petra.dvoda.cz \
    --to=kzak@redhat.com \
    --cc=david-b@pacbell.net \
    --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