[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Create task (logical group of files)?

From: Ryan Schmidt <subversion-2007a_at_ryandesign.com>
Date: 2007-03-26 09:53:54 CEST

On Mar 26, 2007, at 02:10, Henry LS wrote:

>> Why wouldn't you just check out the entire set of files? Work on the
>> files you need to work on, then commit them. Maybe for your next
>> "task" you'll need different files, and you'll already have them
>> since you checked out everything.
> I used to do what you said above when working on my previous
> project. However for the current one, we have a group of 15
> developers frequently update the system and we normally have 2-3
> ppl working on the same subsystem...

Ok, no problem in Subversion...

> So in any minute, the local copy could become a outdated legacy
> version.

Yessss.... but so what? Either your changes can stand alone, in which
case this is not a problem, or your changes depend on the other
developers', in which case you should coordinate your work with those
other developers.

> We are kin to check out as less code as possible

If the reason here is just to save disk space, then I can only point
out that Subversion philosophy is that disk space is cheap. If the
concern is bandwidth, then it needn't be, since Subversion only
transmits deltas over the wire. The initial checkout will take some
time if you have many and/or very large files, but after that, you
have it on your machine, and when you update you will only receive
the updates, which should be relatively quick unless you are changing
many large (e.g. binary) files very often.

> and always try to test our development with the newest runnable
> code from other team members kept in a centralized version control
> system. Not quite sure if this is achievable though...Still trying
> to work it out.

If it's essential that all developers always have the absolutely
latest code the instant it's checked in, consider setting up a commit
mailing list or RSS feed to which your developers subscribe. When
they see a new revision committed, they can update their working
copies to retrieve it.

To reply to the mailing list, please use your mailer's Reply To All  
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Mar 26 09:54:19 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.