git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Sean" <seanlkml@sympatico.ca>
To: "Daniel Barkalow" <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: [RFD] Overlapping projects
Date: Tue, 10 May 2005 08:04:54 -0400 (EDT)	[thread overview]
Message-ID: <4385.10.10.10.24.1115726694.squirrel@linux1> (raw)
In-Reply-To: <Pine.LNX.4.21.0505100040320.30848-100000@iabervon.org>

On Tue, May 10, 2005 12:56 am, Daniel Barkalow said:
> It seems to me like projects like cogito which are based on a core which
> is itself a project and which is also part of other projects would benefit
> from some sort of support.
>
> In particular, it would be nice if Linus could pull the changes to the
> core without getting the wrapper programs at all.
>
> I'm thinking something like having a head for cogito and a head for git in
> the same repository, where the trees for git only have the core files, and
> the commits for cogito have, in addition to a tree with only the
> cogito-specific files, a reference to a git commit that they include.
>
> It seems to me like this area contains a brilliant idea that I haven't
> had so far, and maybe someone can come up with it.
>

That sounds like a great idea and shouldn't need any brilliant ideas to
implement.  Just need to push a little more multi-head handling down into 
 git.  The Cogito build process could then include a checkout of the
git-core branch.  Would be much cleaner than the way it is handled now.

Sean



      parent reply	other threads:[~2005-05-10 11:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-10  4:56 [RFD] Overlapping projects Daniel Barkalow
2005-05-10  5:31 ` Junio C Hamano
2005-05-10  5:51   ` Daniel Barkalow
2005-05-10  6:19     ` Junio C Hamano
2005-05-10 12:04 ` Sean [this message]

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=4385.10.10.10.24.1115726694.squirrel@linux1 \
    --to=seanlkml@sympatico.ca \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.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).