Ruslan Ermilov wrote: > > > I was going to ask in the other mail if some repo surgery had taken > > place. The last time this happened to me, someone had perpetrated > > a repo surgury and something about when I and the mirror synced > > broke things in a way that screwed me (and I think one or two others) > > over. > > > Yes, the repo-surgery was done some time ago, and it looks like you > were hit by it. > > > [brane-dead] /usr/src/contrib # diff -ud ~ianf/complete.c,v /home/ncvs/sr= > c/contrib/libreadline/complete.c,v=20 > > --- /home/ianf/complete.c,v Mon Oct 18 09:02:43 2004 > > +++ /home/ncvs/src/contrib/libreadline/complete.c,v Mon Oct 18 09:02:= > 43 2004 > > _at__at_ -1,4 +1,5 _at__at_ > > head 1.9; > > +branch 1.1.1; > > access; > > symbols > > v5_0:1.1.1.9 > > > > This is the diff of the ,v file. The one in ~ianf was moved out > > of CVSROOT after a cvsup that changed nothing. An immediate > > subsequent cvsup produced a ,v file with this difference. > >=20 > This explains it. The surgery returned this file on a vendor branch, > adding this "branch 1.1.1;" line to an RCS file. Are you by chance > ALWAYS using the -s option to cvsup(1)? I never run cvsup with -s Root's crontab: #minute hour mday month wday # 0 0 * * * /usr/local/bin/cvsup /root/supfile-cvs Ian -- Ian FreislichReceived on Thu Oct 21 2004 - 08:57:54 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:18 UTC