questions on development(7)

Tom Evans at
Fri Nov 9 07:09:47 PST 2007

On Fri, 2007-11-09 at 21:49 +0800, OutbackDingo wrote:
> well thats kinda hard to do with CVS, though other revision systems such
> as mercurial, bazaar, git and perforce, even subversion do it well,
> there is also a mercurial respository for FreeBSD out there some where
> On Fri, 2007-11-09 at 05:36 +0000, Aryeh M. Friedman wrote:
> > >>
> > >> 2. If yes to #1 how do I setup keeping everything except my modified
> > >> code in sync (and if possible to retro activally apply patchs from the
> > >> local branch unto the main source tree [/usr/src2])
> > >
> > > You won't be able to commit to the BSD repo from your server.  I
> > > think you should treat your repo as read only and use cvsup to keep
> > > it up to date.  At least that's what I do.
> > 
> > What I meant was how do I keep from clobbering my local changes?
> > 

(Nothing like top posting to destroy the thread flow)

OutbackDingo is incorrect. That is the entire purpose of CVS, otherwise
they might as well call it VS..

Your /usr/src will be a checkout of a particular branch of freebsd
(called a working copy). You periodically update your cvs repository
(where you checkout from) with the latest freebsd commits. 
When you wish to, you update your working copy from your repository by
issuing a 'cvs up'. This merges changes in the repository into your
local copy, merging in with the local changes.
When you want to see what has changed since you last did a 'cvs up',
issue a 'cvs -n up'.
When you want to see the local modifications in your working copy, issue
a 'cvs diff'.

Read the cvs red-bean book for more info.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url :

More information about the freebsd-current mailing list