Date: Sat, 24 Jun 2000 03:49:58 +0900 From: "Akinori -Aki- MUSHA" <knu@idaemons.org> To: kstewart@3-cities.com Cc: peter@FreeBSD.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/ufs/ffs ffs_softdep.c softdep.h Message-ID: <86snu4b5bd.wl@localhost.local.idaemons.org> In-Reply-To: In your message of "Fri, 23 Jun 2000 09:59:55 -0700" <3953978B.D3EAD145@3-cities.com> References: <200006221927.MAA49212@freefall.freebsd.org> <39532EE4.B536C551@3-cities.com> <86wvjgbu09.wl@localhost.local.idaemons.org> <3953978B.D3EAD145@3-cities.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At Fri, 23 Jun 2000 09:59:55 -0700,
Kent Stewart <kstewart@3-cities.com> wrote:
> True! My point is that the update isn't occuring. I just happened to
> be sitting at the computer when the message flashed by on the window.
> I would have never seen it otherwise. I don't usually scan the log for
> a cvsup failure. Perhaps, this is something I should be doing but
> people get used to cvsup always working. The file may be bad but cvsup
> worked. This time cvsup didn't update the files. If people run cvsup
> as an unattended cron job, they will never see the two failure
> messages.
>
> I ran cvsup a second time and those two lines were the only messages.
> I unlinked the files and did a cvsup, which worked.
That's not your fault anyway. Something like that will happen merely
because CVSup (and CVS) doesn't know about symlinks.
--
/
/__ __
/ ) ) ) ) /
Akinori -Aki- MUSHA aka / (_ / ( (__( @ idaemons.org / FreeBSD.org
"We're only at home when we're on the run, on the wing, on the fly"
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86snu4b5bd.wl>