From: "Geoff Russell" <geoffrey.russell@gmail.com>
To: git@vger.kernel.org
Subject: importing cvs logical modules
Date: Thu, 25 May 2006 14:18:25 +0930 [thread overview]
Message-ID: <93c3eada0605242148u4656bc31p96d84a16703f0fe0@mail.gmail.com> (raw)
Hi,
Firstly, the code to automagically
repack a git repository on-the-fly during a big load has solved one of
my problems - thanks, it is great. Unfortunately it has bought me to
showstopper number 2.
- cvs modules.
cvs allows you to define modules which rearrange the physical repository into
a different logical structure. This sounds great and we use it, but it gives
us other headaches because "cvs update" doesn't always do the right
thing with these modules.
Furthermore cvsps doesn't appear to handle this module feature at all and
is tricked into thinking that rearranged directories come from somewhere
else and issues its "file xxx doesn't match strip_path" message.
I have tried to hack cvsps to go around the problem, but without success.
Another alternative that I thought might be easier would be to unload the cvs
repository in clean pieces - each being a git repository. Then to join the
git repositories together in the desired way. I think this would be
generally useful and not just solve my problem.
e.g. Suppose I have 3 git repositories: Progs, xxxx, yyyy
Progs/.git
xxxx/.git
yyyy/.git
I'd like to make 1 git repository Progs with xxxx and yyyy as child trees.
Progs/.git
Progs/xxxx
Progs/yyyy
Does this sound useful to anyone else, or is it already possible?
Cheers,
Geoff Russell.
next reply other threads:[~2006-05-25 4:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 4:48 Geoff Russell [this message]
2006-05-25 4:56 ` importing cvs logical modules Jakub Narebski
2006-05-25 5:01 ` Junio C Hamano
2006-05-25 6:02 ` Geoff Russell
2006-05-25 6:16 ` Martin Langhoff
2006-05-25 6:59 ` Geoff Russell
2006-05-25 7:02 ` Jakub Narebski
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=93c3eada0605242148u4656bc31p96d84a16703f0fe0@mail.gmail.com \
--to=geoffrey.russell@gmail.com \
--cc=geoff@austrics.com.au \
--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).