On Tue, 25 Oct 2005 16:21:07 -0500 (CDT) Luc Teirlinck <[EMAIL PROTECTED]> wrote:
> Steven Berman wrote: > > Has no one else experienced this with today's sources? If not, could > I somehow have gotten a corrupted source that isn't fixed by updating? > How should I proceed from here? > > I am not exactly the biggest CVS expert around, but what could have > for instance happened is that you reverted something to an earlier > version and forgot to ever revert back. Or you could have set sticky > tags in various other ways. See `(cvs)Sticky tags'. I believe that > `cvs -z3 update -A' should get rid of any sticky tags, assuming that > would be your problem. > > Sincerely, > > Luc. [The following paragraph was sent yesterday mistakenly just to Luc, sorry!] I have never done anything with my Emacs CVS sources other than `cvs up' and `cvs up -d' (*not* -D). My last update before today was October 20, and that was unproblematic. I think I'll wait till tomorrow, update again, and if that doesn't work, I guess I'll just check out the whole CVS tree from scratch. Unless anyone has another idea... [Now:] Well I tried `cvs up -d' again this morning, but to no avail. Then as a last attempt before resorting to a pristine full check out I did `cvs up -PACd' -- and that worked. I would be surprised if there really was a sticky tag, since I certainly reverted no files since October 20. I think I did have one or two locally modified files, so maybe the -C did the trick, though I don't remember modifying anything between October 20 and yesterday... Steve Berman _______________________________________________ Emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
