Re: [PATCH] git-cvsimport: Add -N option to force a new import

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Matt McCutchen <matt@...>
Cc: Junio C Hamano <gitster@...>, <git@...>
Date: Thursday, October 25, 2007 - 3:45 pm

torsdag 25 oktober 2007 skrev Matt McCutchen:

None, but there should be. I also think cvsps should be included in the git 
repo since it is required and AFAIK, only git people maintain it. 

Now I don't use cvsimport to import my CVS repos, so I'll pass on adding test 
cases. It is a non-trivial task 

I did it for cvsexportcommit which didn't have any tests when I started 
hacking it.

-- robin

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH] git-cvsimport: Add -N option to force a new import, Matt McCutchen, (Wed Oct 24, 7:28 pm)
Re: [PATCH] git-cvsimport: Add -N option to force a new import, Robin Rosenberg, (Thu Oct 25, 3:45 pm)
Re: [PATCH] git-cvsimport: Add -N option to force a new import, Johannes Schindelin, (Thu Oct 25, 5:56 am)