Date: Fri, 27 Feb 1998 02:11:35 -0800 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: Eivind Eklund <eivind@yes.no> Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-CVSROOT@FreeBSD.ORG Subject: Re: cvs commit: CVSROOT avail Message-ID: <703.888574295@time.cdrom.com> In-Reply-To: Your message of "Fri, 27 Feb 1998 10:55:41 %2B0100." <19980227105541.55943@follo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> You scenario: > > do-local-cvs > > cvs checkout ls > <hack-hack-hack> > > cvscommit > <oh damn! it was out-of-date!> Happens very rarely, actually, since I sync my cvs repository at least 3-4 times a day from freefall. But yes, if I think I'm going to run into anything like that then I simply don't use the "cvscommit" convenience function, I toggle do-remote-cvs once and do cvs commit followed by cvs update if a conflict comes up. > I really can't see the 'easier ways' part - is there something I'm > missing, or something you're missing, or are we just disagreeing on > what is easy here? I guess it comes down to whether or not you consider thwacking the CVS/Root file easier or the CLI option easier - it's sort of the same to me given that I've been using the aformentioned shell functions for so long that the "stateful model" works for me more than having to think of different cvs aliases depending on whether I'm working locally or remotely. But I'm willing to concede that this comes entirely down to what one considers easier. :) Jordan 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?703.888574295>