From: James Purser <purserj@ksit.dynalias.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org, Petr Baudis <pasky@ucw.cz>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [RFC] Support projects including other projects
Date: Thu, 12 May 2005 15:37:12 +1000 [thread overview]
Message-ID: <1115876231.3085.4.camel@kryten> (raw)
In-Reply-To: <Pine.LNX.4.21.0505120057250.30848-100000@iabervon.org>
On Thu, 2005-05-12 at 15:19, Daniel Barkalow wrote:
> If you think about it as git and cogito being entirely separate projects,
> where users would be expected to have the right version of git most of the
> time (or ever), this is true. But I think that cogito is as closely tied
> to git as the kernel is to kbuild or kconfig; the difference is that git
> is not solely available with cogito, like kbuild is solely available with
> the kernel.
I tend to disagree with you on this point. Cogito and Git share
arelationship more akin to xorg and gnome and this is something I think
Linus intended so that it would be very easy to build a layer on top of
the git toolset. Cogito is great and it fills a need but give it time
and other implementations and tool sets will come along that may
supersede it.
--
James Purser
http://ksit.dynalias.com
next prev parent reply other threads:[~2005-05-12 5:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 4:23 [RFC] Support projects including other projects Daniel Barkalow
2005-05-12 4:52 ` Junio C Hamano
2005-05-12 5:19 ` Daniel Barkalow
2005-05-12 5:37 ` Junio C Hamano
2005-05-12 6:04 ` Daniel Barkalow
2005-05-12 6:28 ` Junio C Hamano
2005-05-12 16:51 ` Daniel Barkalow
2005-05-12 17:24 ` David Lang
2005-05-12 18:47 ` Junio C Hamano
2005-05-12 19:12 ` Daniel Barkalow
2005-05-12 6:14 ` Junio C Hamano
2005-05-12 5:37 ` James Purser [this message]
2005-05-12 5:46 ` Daniel Barkalow
2005-05-12 6:33 ` James Purser
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=1115876231.3085.4.camel@kryten \
--to=purserj@ksit.dynalias.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--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).