Re: what happend with hwclock patches?

[David Brownell <david-b@pacbell.net>]

On Wednesday 07 March 2007 2:42 am, Karel Zak wrote:
>  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.

Something like that would probably be a good thing.   The visibility that
patches are finally getting released will help restart machinery that's had
sand in its gears for way too long.


>  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.)

Thing is, distros are more likely to notice an updated util-linux package
than Yet Another Patch That Should Have Come From Upstream ... and the issue
is not _my_ distro (heck, I patched my systems directly) but every distro
that could potentially run a 2.6.21 kernel.  I am *NOT* in touch with many
such maintainers.  


> On Tue, Mar 06, 2007 at 08:06:27PM -0800, David Brownell wrote:
> 
> > 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

Well, by active development I included "merging patches submitted" e.g. hwclock,
but it's also rather conventional to have patches show up on mainline instead of
only on branches.  See for example the kernel tree, or essentially any other tree...

It stiil doesn't *show* that development in the usual way.  Attributing the issue
to gitweb isn't relevant; lots of people don't know more than "git pull", and if
that doesn't give them updates, they effectively didn't happen.


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

That's good to know.  As you're well aware, the fact that this package
is an orphan has made trouble.  No real release since 2005, etc ...

- Dave