Junio C Hamano wrote:
Todd Zullinger <tmz@xxxxxxxxx> writes:
Chris has been busy with other things for a while. I started helping
with git package maintenance only in the last 6 months or so. Over
time, the spec file we have has drifted a bit from what is in git.git,
though not terribly so. I need to spend some time and look at what,
if any, changes in the Fedora spec file would be good candidates for
submitting to git.git. I have been primarily concerned with making
things work cleanly on Fedora and RHEL/CentOS though, so some of the
changes may not be as generic as they ought to be if they are to be
included in git.git.
I use the one in git.git only to cut the Fedora 9 packages for consumption
by k.org people. I do not know what their upgrade plans are, but last
time they upgraded from FC 5 to Fedora 9 I had to scramble around and find
an i386 box to produce binaries (the machine available to me at k.org is
amd64). Perhaps I should start preparing Fedora 11 environment now it is
finally released, but before that I need to procure a new development box
to host it in a vm, as the current box that is the primary integration
machine for git and that hosts the Fedora 9 i386 vm has got too tight and
I've been limping along; it does not have enough room to host another vm
(and it is not even hardware vm capable)...
The general idea is when we aren't getting security updates for our
current install base, that is when we (k.org) will make the move to upgrade.
That said, since 11 just came out I'm going to have to start considering
and working on an upgrade plan, but I wouldn't expect that to be getting
to a point where it would affect you for a few months yet, and I would
hate to upgrade to Fedora 11 before it's had a chance to settle and stew.
- John 'Warthog9' Hawley
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html