git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Langhoff <martin.langhoff@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Darrin Thompson <darrint@progeny.com>, git@vger.kernel.org
Subject: Re: Merges without bases
Date: Fri, 26 Aug 2005 21:17:03 +1200	[thread overview]
Message-ID: <46a038f905082602176f9eef5d@mail.gmail.com> (raw)
In-Reply-To: <7vvf1tps9v.fsf@assigned-by-dhcp.cox.net>

On 8/26/05, Junio C Hamano <junkio@cox.net> wrote:
> their core GIT tools come from.  But how would _I_ pull from
> that "My Project", if I did not want to pull unrelated stuff in?

and then... 

> What I think _might_ deserve a bit more support would be a merge
> of a foreign project as a subdirectory of a project.  Linus

tla has an interesting implementation (and horrible name) for
something like this. In Arch-speak, they are called 'configurations',
a versioned control file that describes that in subdirectory foo we
import from this other repo#branch.

In cvs, you just do nested checkouts, and trust a `cvs update` done at
the top will do the right thing;  and in fact recent cvs versions do.

After using cvs and arch for a while, my opinion is that all this
stuff is _bad_, and you want a makefile that pulls the projects
together when you build them. Different projects are going to use
different SCMs anyway, and you'll have to live with how to tag a
release across repositories/scms, and I haven't seen any answer I
like.

cheers,


martin

  parent reply	other threads:[~2005-08-26  9:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-25 21:10 Merges without bases Darrin Thompson
2005-08-25 21:29 ` Darrin Thompson
2005-08-25 22:26 ` Junio C Hamano
2005-08-25 22:59   ` Darrin Thompson
2005-09-08 18:01     ` Tim Ottinger
2005-08-26  4:09   ` Daniel Barkalow
2005-08-26  8:00     ` Junio C Hamano
2005-09-09 12:02       ` Eric W. Biederman
2005-08-26  9:17   ` Martin Langhoff [this message]
2005-08-26 16:37     ` Daniel Barkalow
2005-08-27  6:48       ` Martin Langhoff
2005-08-27 20:49         ` Daniel Barkalow

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=46a038f905082602176f9eef5d@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=darrint@progeny.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).