From: David Brownell <david-b@pacbell.net>
To: Karel Zak <kzak@redhat.com>
Cc: List util-linux-ng <util-linux-ng@vger.kernel.org>
Subject: Re: what happend with hwclock patches?
Date: Wed, 7 Mar 2007 12:08:24 -0800 [thread overview]
Message-ID: <200703071208.25365.david-b@pacbell.net> (raw)
In-Reply-To: <20070307190137.GA26835@petra.dvoda.cz>
On Wednesday 07 March 2007 11:01 am, Karel Zak wrote:
> On Wed, Mar 07, 2007 at 09:42:49AM -0800, David Brownell wrote:
> > > 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
> >
> > Well, by active development I included "merging patches submitted" e.g. hwclock,
>
> Sure, but the util-linux-ng is still not in the condition when I'll
> merging patches ASAP. There are tons of others and more important
> patches, there wasn't any tests, there was broken build system ...
> Don't forget that the code has been unmaintained for almost 2 years.
I'd call some of that "catching up with the backlog", which is
of course one kind of development. OK, so I'm picky; shoot me!
I was pleased to see tests getting added. It's as if this were
becoming a real software project ... ;)
> Please, be patient at least for next 1-2 months.
>
> BTW, "active" also means that someone answers your mails. I hope you
> see the change :-)))
Yes indeedy!!
>
> Also see:
> http://userweb.kernel.org/~kzak/util-linux-ng/
>
>
> I believe there is more light now :-)
Yes. Worth posting a status update to LKML?
- Dave
prev parent reply other threads:[~2007-03-07 20:15 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 ` what happend with hwclock patches? Karel Zak
2007-03-07 17:42 ` David Brownell
2007-03-07 19:01 ` Karel Zak
2007-03-07 20:08 ` David Brownell [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=200703071208.25365.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=kzak@redhat.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