[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

hurd/glibc.git and merging

From: Roland McGrath
Subject: hurd/glibc.git and merging
Date: Wed, 9 May 2012 13:57:38 -0700 (PDT)

There is some agitation in libc circles about the state of Hurd
support.  I'd like to get a lot of the low-hanging-fruit Hurd
changes merged into libc ASAP.

I've been looking at git://git.sv.gnu.org/hurd/glibc.git and read
enough about topgit to have a general sense of how the branches are
meant to be used.  I've looked at a small handful of the branches
and some seem quite trivial to merge.  But they are not really
merge-ready.  Some are completely lacking ChangeLog entries, and I'd
rather have these written by the person who made the change than do
it myself.  Some have incomplete ChangeLog entries (not mentioning
every file touched).  Probably all are missing proper copyright year
updates for the current protocol (which is to collapse down to a
single year range ending in 2012).

Unless I've been even more remiss than I thought I'd been, some of
these changes were never posted for my review at all.  I guess I was
sufficiently remiss for a long time that people could reasonably
have given up, and I'm sorry for that.  I'd like to remedy the
situation now.

Certainly the easiest thing for me is if each change is turned into
a git branch that is suitable for direct merging into the libc
trunk, or a git-am-friendly posting.  But since everybody's time is
limited, I'm willing to help out with the tedium to some degree.

I think we could get through the vast majority, which are simple
cases, with no more than a day of focused work.  Who wants to help?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]