Re: parsecvs tool now creates git repositories

From: Martin Langhoff <martin.langhoff@gmail.com>
Date: Apr 4, 2006, 02:42 UTC
Message-ID: <46a038f90604031942w779894b8p5ef221482a70a301@mail.gmail.com>
In-Reply-To: <1144117473.2303.132.camel@neko.keithp.com>

On 4/4/06, Keith Packard <keithp@keithp.com> wrote:

Show 9 quoted lines

> On Tue, 2006-04-04 at 14:16 +1200, Martin Langhoff wrote:
>
> > Meh, had you done it in Perl, I'd be helping you with the Pg repo,
> > attic files and ensuring that files created on a branch and then put
> > into HEAD are handled gracefully. (But you'll get Linus' and Junio's
> > attention. Smarty cookie.)
>
> I think those parts are working correctly, I've had plenty of examples
> of that kind of adventure.

Cool. What's the matter with the Pg repo? (Where can I get hold of that repo?)

> > Does it run incrementally? Can it discover non-binary files and pass -kk?
>
> It doesn't run incrementally, and it unconditionally passes -kk. It's

I thought that the .git-cvs directory it created was to be able to run incrementally (btw, I think it's fair game to create subdirs inside .git for this kind of status-tracking). And passing -kk uncoditionally is destructive in some cases (I know... git-cvsimport does it, and I want to fix that). If you can ask rcs about the mode if the file and not pass -kk for binary files...

> currently using rcs to check out versions of the files, so it should
> deal with binary content as well as rcs does. Is there something magic I
> need to do here? Like for DOS?

We'll let DOS take care of itself ;)