Re: [PATCH] git-cvsimport: Add -N option to force a new import
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Oct 25, 2007, 09:56 UTC
- Message-ID
- <Pine.LNX.4.64.0710251055590.25221@racer.site>
- In-Reply-To
- <1193284913.2619.23.camel@mattlaptop2>
Hi,
On Thu, 25 Oct 2007, Matt McCutchen wrote:
Show 16 quoted lines
> On Wed, 2007-10-24 at 20:17 -0700, Junio C Hamano wrote: > > Matt McCutchen <matt@mattmccutchen.net> writes: > > > > > I had a git repository for development of rsync and wanted to start > > > importing the upstream CVS with git-cvsimport, but git-cvsimport saw > > > that the git repository existed and insisted on updating a previous > > > import. This patch adds an -N option to git-cvsimport to force a new > > > import and updates the documentation appropriately. > > > > Sounds like a useful addition. Tests? > > Are there existing tests for git-cvsimport somewhere whose example I > could follow? (I didn't see any in t/ .) If not, I suppose I will just > write a simple script that runs git-cvsimport with and without -N and > with and without an existing, empty git repository and checks that the > right things happen.
My best bet: t/t9200-cvsexportcommit.sh
Hth, Dscho