git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
	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 21:01:28 -0700	[thread overview]
Message-ID: <42969B98.7070701@zytor.com> (raw)
In-Reply-To: <7vk6ll2vde.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:
> 
> HPA> Not "just" an installation convenience.  Right now cogito and git-core
> HPA> *conflict*.  That's why cogito really needs to be broken out from
> HPA> git-core, so git-core can be updated independently.
> 
> What I learned from this thread are these:
> 
>  (1) CGI does not need Cogito but just needs core GIT.
>  (2) Nobody said he uses Cogito on kernel.org machines.
>  (3) But Cogito is installed nevertheless.
>  (4) Installation of Cogito is done via RPM "with Makefiles and
>      spec files" and both Cogito and core GIT comes bundled in.
>  (5) I gather that there is no core GIT only RPM (nobody said
>      this explicitly in this thread, though, so I may be
>      mistaken about this point).
> 
> And that was where my comment about "just an installation
> convenience" came from.
> 
> If somebody said Cogito _is_ used on kernel.org machines, then I
> would not have said "just" nor "convenience".  That would mean
> there is a real need to have Cogito and having just core GIT
> would not be enough.

I, for one, use Cogito on the kernel.org machines.

	-hpa

  reply	other threads:[~2005-05-27  4:00 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
2005-05-27  1:50               ` H. Peter Anvin
2005-05-27  3:36                 ` Junio C Hamano
2005-05-27  4:01                   ` H. Peter Anvin [this message]
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=42969B98.7070701@zytor.com \
    --to=hpa@zytor.com \
    --cc=braddr@puremagic.com \
    --cc=david@dgreaves.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --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 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).