On 5/25/06, Martin Langhoff <martin.langhoff@xxxxxxxxx> wrote:
On 5/26/06, Cameron McBride <cameron.mcbride@xxxxxxxxx> wrote: Ok. You might want to retain that latest, it has some further fixes ;-)
sounds good.
Yes, I was guessing as much. I am still curious about what parameters (and in what order) cvs 1.11.7 sends...
sure! now that I know CVS_CLIENT_LOG exists ... ;) It points in basically the same direction, which is to say the newer client passes an 'Argument -- ' which is what git-cvsserver seems to be choking on. The 'in' versions of the two noup: cvs 1.11.1p1 that failed plane cvs update work: cvs 1.11.17 that worked --- cvs_noup.log.in 2006-05-25 23:44:21.000000000 -0400 +++ cvs_work.log.in 2006-05-25 23:48:38.000000000 -0400 @@ -1,6 +1,7 @@ Root /export/home/cameron/ws/git_test/ntropy.git -Valid-responses 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 +Valid-responses 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 Notified Module-expansion Wrapper-rcsOption M Mbinary E F MT valid-requests +Argument -- Directory . /export/home/cameron/ws/git_test/ntropy.git/master Entry /.gitignore/1.1/// Thanks for your help! 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