Re: Importing from CVS issues
- From
- Alex Bennee <alexjb@transitive.com>
- Date
- Aug 16, 2005, 13:48 UTC
- Message-ID
- <1124200099.7444.37.camel@okra.transitives.com>
- In-Reply-To
- <u5toe7y2i28.fsf@fidgit.hq.vtech>
On Tue, 2005-08-16 at 14:16 +0200, David Kågedal wrote:
Show 13 quoted lines
> Alex Bennee <kernel-hacker@bennee.com> writes: > > > Before the import script finally dies with: > > > > WARNING: revision 1.3.2.1 of file > > scripts/xmltools/t/data/gzip/DO-NOT-BACKUP on unnamed branch > > DONE; creating master branch > > cp: cannot stat `/export/test/cvstogit/.git/refs/heads/origin': No such > > file or directory > > Was this done with an empty destination dir? I've seen similar things > happen in a dir where an interrupted cvs import was done previously, > and the 'origin' branch was never created.
Yes, in fact I let the script create the new destination dir. So I don't think its an issue with stale data from a previous attempt being left around.
>
-- Alex Bennee - alexjb@transitive.com "The world is beating a path to our door" -- Bruce Perens, (Open Sources, 1999 O'Reilly and Associates)