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. 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 :-))) > 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. $ git clone git://git.kernel.org/pub/scm/utils/util-linux-ng/util-linux-ng.git util-linux-ng $ git checkout -f devel $ git log Well, we're very exotic. We use branches. There is: $ cat .git/remotes/origin URL: git://git.kernel.org/pub/scm/utils/util-linux-ng/util-linux-ng.git Pull: refs/heads/master:refs/heads/origin Pull: refs/heads/devel:refs/heads/devel after "git clone", so I don't see any problem with "git pull". You should see updates in the 'devel' branch as well. Also see: http://userweb.kernel.org/~kzak/util-linux-ng/ I believe there is more light now :-) Karel -- Karel Zak <kzak@xxxxxxxxxx> - To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
