From 74d563f20fbdc2ed431f20b24c9a84a3ff811b93 Mon Sep 17 00:00:00 2001 From: "http://schmonz.livejournal.com/" Date: Thu, 30 Jul 2009 01:45:09 -0400 Subject: [PATCH] progress --- doc/post-commit/discussion.mdwn | 2 ++ 1 file changed, 2 insertions(+) diff --git a/doc/post-commit/discussion.mdwn b/doc/post-commit/discussion.mdwn index c15396978..bbe529106 100644 --- a/doc/post-commit/discussion.mdwn +++ b/doc/post-commit/discussion.mdwn @@ -58,3 +58,5 @@ In case you're lucky enough not to know, cvs adds on directories are weird -- th I was able to work out that when I'm seeing this page save misbehavior, my plugin is somewhere inside `system("cvs", "-Q", "add", "$file")`, which was never returning. If I changed it to anything other than cvs it iterated correctly over all the parent dirs which needed to be added to CVS, in the proper order. (cvs add isn't recursive, sadly.) Can you offer an educated guess what's going wrong here? --[[Schmonz]] + +> Got `rcs_recentchanges` working, believe it or not, thanks to [cvsps](http://www.cobite.com/cvsps/). If I can figure out this interaction between the post-commit hook and `cvs add` on directories, the CVS plugin is mostly done. Could it be a locking issue? Where should I be looking? Any suggestions appreciated. --[[Schmonz]] -- 2.32.0.93.g670b81a890