From: "J.H." <warthog19@eaglescrag.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Todd Zullinger <tmz@pobox.com>, Jeff Garzik <jeff@garzik.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [bug] git cannot find "git pull"?
Date: Thu, 11 Jun 2009 23:52:18 -0700 [thread overview]
Message-ID: <4A31FB22.7030500@eaglescrag.net> (raw)
In-Reply-To: <7viqj2c9rs.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> Todd Zullinger <tmz@pobox.com> 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
next prev parent reply other threads:[~2009-06-12 6:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 0:10 [bug] git cannot find "git pull"? Jeff Garzik
2009-06-12 1:17 ` Todd Zullinger
2009-06-12 2:44 ` Junio C Hamano
2009-06-12 3:18 ` Todd Zullinger
2009-06-12 5:15 ` Junio C Hamano
2009-06-12 6:52 ` J.H. [this message]
2009-06-12 11:30 ` Jeff Garzik
2009-06-12 19:10 ` Jeff Garzik
2009-06-12 20:26 ` Todd Zullinger
2009-06-12 20:49 ` Jeff Garzik
2009-06-13 15:04 ` Todd Zullinger
2009-06-13 17:22 ` Jeff Garzik
2009-06-13 17:36 ` Todd Zullinger
2009-06-15 17:23 ` Jeff Garzik
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=4A31FB22.7030500@eaglescrag.net \
--to=warthog19@eaglescrag.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jeff@garzik.org \
--cc=tmz@pobox.com \
/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;
as well as URLs for NNTP newsgroup(s).