Date: Sun, 16 Mar 2003 11:58:07 -0800 From: Sean Chittenden <sean@chittenden.org> To: Nate Williams <nate@yogotech.com> Cc: Sergey Babkin <babkin@bellatlantic.net>, hackers@FreeBSD.ORG Subject: Re: making CVS more convenient Message-ID: <20030316195807.GH66903@perrin.int.nxad.com> In-Reply-To: <15988.52765.777500.37926@emerger.yogotech.com> References: <3E73DCF7.80490FA6@bellatlantic.net> <15988.49648.483313.383942@emerger.yogotech.com> <3E74CC37.DF83EE46@bellatlantic.net> <15988.52765.777500.37926@emerger.yogotech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--+JUInw4efm7IfTNU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > > Yet another idea is to be able to make "local commits" with committing > > them to the central remote repository later. >=20 > I'd do the reverse, since the possibility of synchronization problems > are a huge deal. Imagine if someone 'snuck' in and made a commit in > the master tree after your local commit was made, but before 'later' > occurred and your cache pushed it out to the master tree. >=20 > If you only allow the commit if it can occur locally, you're ensuring > that the cache can't get out of date with local changes. I tried > something like the above (cause it was easier to implement), and it > worked most of the time. However, the times it didn't work it was a > royal pain in the *ss to cleanup and get the original commit back out. It'd be cool to teach CVSup to ignore updating certain files that have been marked locally as "dirty" or "in flux" until they've been committed through to the master repo. Even better would be to have CVSup ignore making changes to designated branches (RELENG_5_SEANC). The corollary to that would be to teach cvs(1) to commit changes to the master repo that have been made to the local repo. Version number sync would be a problem, but it'd be really cool to be able to do that. With a branch mapping layer (RELENG_5_SEANC -> HEAD), people could actually get back into the habit of using CVS as a development tool instead of just a way of publishing finalized work. Maybe the above changes could be rolled into the rewrite of CVSup in C. CVSup -> C ld cvsup -lkse cvsup(1) -> base system ::grin:: -sc --=20 Sean Chittenden --+JUInw4efm7IfTNU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Comment: Sean Chittenden <sean@chittenden.org> iD8DBQE+dNdO3ZnjH7yEs0ERAquTAJ95NC5Au5Et3mJ8PDDTaNSnrQPcggCeJNqj +wKleHhn2ctN2IvGV87J38Y= =v+3J -----END PGP SIGNATURE----- --+JUInw4efm7IfTNU-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030316195807.GH66903>