From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>, Junio C Hamano <junkio@cox.net>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
"Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: [RFC/PATCH] commit-tree: bump MAX_PARENTS to 128
Date: Tue, 27 Feb 2007 11:31:52 +0000 [thread overview]
Message-ID: <200702271131.57856.andyparkins@gmail.com> (raw)
In-Reply-To: <20070227105212.GA21757@coredump.intra.peff.net>
On Tuesday 2007 February 27 10:52, Jeff King wrote:
> A year or so ago, I started using git, and imported all of my CVS repos
> to git. I did each class directory separately, reasoning that each
> represented a separate history. This can end up being unwieldy, because
> there are dozens of repositories; I would now like to group them in the
> same repo for ease of clone/fetch.
It doesn't have fetch or clone support, but perhaps my poorman's submodule
code will help you a bit, until real submodule support appears in git.
http://marc2.theaimsgroup.com/?l=git&m=116662031219222&w=2
I've found it useful for myself, and with a little bit of massaging I don't
think it would be hard to put fetch support in. I think it just needs a way
of telling the remote end to switch GIT_DIR to a different directory.
"Merges" are handled by simply sorting out any conflicts in the module file
(basically you pick one of the submodule commits) just as you would with any
other file.
As I say - not fabulous, but gets me by.
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
next prev parent reply other threads:[~2007-02-27 11:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 12:15 [RFC/PATCH] commit-tree: bump MAX_PARENTS to 128 Jeff King
2007-02-26 14:31 ` Shawn O. Pearce
2007-02-26 16:38 ` Johannes Schindelin
2007-02-27 8:16 ` Junio C Hamano
2007-02-27 8:19 ` Jeff King
2007-02-27 10:23 ` Junio C Hamano
2007-02-27 10:52 ` Jeff King
2007-02-27 11:06 ` Junio C Hamano
2007-02-27 11:31 ` Andy Parkins [this message]
2007-02-27 11:39 ` Jeff King
2007-02-27 14:04 ` Jakub Narebski
2007-02-27 15:46 ` Johannes Schindelin
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=200702271131.57856.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=peff@peff.net \
--cc=spearce@spearce.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).