Does cvs commit upstream work? In my testing, I can't get 'cvs ci' to
function on a git repo.
This seems to be broken with v1.3.3 and latest 1.3.3.ged90. The cvs
clients are the same as before 1.11.1p1 and 1.11.17
The cvs client exits with:
Index already exists in git repo
The log (for git version 1.3.3.ged90):
INFO - --------------- STARTING -----------------
DEBUG - Temporary directory is '/tmp/UvaWwud8fs'
DEBUG - req_Root : /export/home/cameron/ws/git_test/ntropy.git
DEBUG - req_Validresponses : ok error Valid-requests Checked-in
New-entry Checksum Copy-file Updated Created Update-existing Merged
Patched Rcs-diff Mode Mod-time Removed Remove-entry
Set-static-directory Clear-static-directory Set-sticky Clear-sticky
Template Set-checkin-prog Set-update-prog Notified Module-expansion
Wrapper-rcsOption M Mbinary E F MT DEBUG -
req_validrequests
DEBUG - SEND : Valid-requests remove add status Entry watchers ci tag
log co Modified Questionable admin Root history valid-requests
Global_option Argumentx annotate Valid-responses Unchanged Directory
rlog Argument expand-modules diff editors update
DEBUG - SEND : ok
DEBUG - Argument : -m
DEBUG - Argument : ncsa mod
DEBUG - req_Directory : localdir=.
repository=/export/home/cameron/ws/git_test/ntropy.git/master path=
directory= module=master
INFO - Received entry line '/README/1.7///' => 'README'
DEBUG - Argument : README
INFO - req_ci : [NULL]
WARN - file 'index' already exists in the git repository
Let me know if any additional information is useful, I didn't have
much time to dig into this.
Cameron
-
: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html