From: Junio C Hamano <junkio@cox.net>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
pasky@ucw.cz, braddr@puremagic.com, nico@cam.org,
david@dgreaves.com, Git Mailing List <git@vger.kernel.org>
Subject: Re: Summary of core GIT while you are away.
Date: Thu, 26 May 2005 16:59:47 -0700 [thread overview]
Message-ID: <7vll618rnw.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20050526232953.GA6215@vrfy.org> (Kay Sievers's message of "Fri, 27 May 2005 01:29:53 +0200")
>>>>> "KS" == Kay Sievers <kay.sievers@vrfy.org> writes:
KS> The cgi doesn't need it. Cogito has the spec file and the
KS> Mekefile with support for it - that was the reason the RPM
KS> made it on the machines there.
Ah, just installation convenience. I see.
next prev parent reply other threads:[~2005-05-26 23:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-14 10:51 Summary of core GIT while you are away Junio C Hamano
2005-05-16 16:10 ` Linus Torvalds
2005-05-16 21:33 ` rev-list/tree committer/author information Junio C Hamano
2005-05-16 22:19 ` Petr Baudis
2005-05-16 22:35 ` Daniel Barkalow
2005-05-16 23:17 ` Junio C Hamano
2005-05-16 22:22 ` Summary of core GIT while you are away Petr Baudis
2005-05-26 0:44 ` Kay Sievers
2005-05-26 1:13 ` Junio C Hamano
2005-05-26 1:53 ` Linus Torvalds
2005-05-26 1:45 ` Linus Torvalds
2005-05-26 20:27 ` Kay Sievers
2005-05-26 20:51 ` Junio C Hamano
2005-05-26 23:29 ` Kay Sievers
2005-05-26 23:59 ` Junio C Hamano [this message]
2005-05-27 1:50 ` H. Peter Anvin
2005-05-27 3:36 ` Junio C Hamano
2005-05-27 4:01 ` H. Peter Anvin
2005-05-27 4:12 ` Junio C Hamano
2005-05-27 4:13 ` H. Peter Anvin
2005-05-27 4:31 ` Junio C Hamano
2005-05-27 5:21 ` Linus Torvalds
2005-05-26 22:11 ` H. Peter Anvin
2005-05-26 22:25 ` Junio C Hamano
2005-05-26 23:59 ` Kay Sievers
2005-05-27 0:16 ` Junio C Hamano
2005-05-27 0:22 ` Kay Sievers
2005-05-27 0:40 ` Junio C Hamano
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=7vll618rnw.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=braddr@puremagic.com \
--cc=david@dgreaves.com \
--cc=git@vger.kernel.org \
--cc=kay.sievers@vrfy.org \
--cc=nico@cam.org \
--cc=pasky@ucw.cz \
--cc=torvalds@osdl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.