Re: Tracking CVS

From: Jon Smirl <jonsmirl@gmail.com>
Date: Jun 23, 2006, 02:18 UTC
Message-ID: <9e4733910606221918r775f49f0l4929f4703281115f@mail.gmail.com>
In-Reply-To: <20060622135831.GB21864@pasky.or.cz>

On 6/22/06, Petr Baudis <pasky@suse.cz> wrote:

Show 19 quoted lines

> Dear diary, on Thu, Jun 22, 2006 at 02:41:16PM CEST, I got a letter
> where Jon Smirl <jonsmirl@gmail.com> said that...
> > I'm tracking cvs using this sequence.
> >
> > cvs update
> > cg rm -a
> > cg commit
> > cg add -r .
> > cg commit
> >
> > Is there a way to avoid the two commits? If you do the add with out
> > the intervening commit it just adds the files back.
>
> I think the most straightforward way is:
>
>         cvs update
>         cg-rm -a
>         cg-status -wns \? | xargs cg-add
>         cg-commit

This doesn't pick up new directories with recursion.

Show 20 quoted lines

>
> If you want to be careful about filenames polluted by non-newline
> whitespaces,
>
>         cg-status -wns \? | tr '\n' '\0' | xargs -0 cg-add
>
> If you want to be safe even with filenames containing newlines, you need
> to go at the Git level:
>
>         git-ls-files -z --others | \
>                 xargs -0 git-update-index --add --
>
> Perhaps we might make a special command which would sync the index set
> with the working copy set...
>
> --
>                                 Petr "Pasky" Baudis
> Stuff: http://pasky.or.cz/
> A person is just about as big as the things that make them angry.
>

-- 
Jon Smirl
jonsmirl@gmail.com