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

RE: vote: checkout a single file

From: Janulewicz, Matthew <MJanulewicz_at_westernasset.com>
Date: 2005-08-18 18:04:08 CEST

On a philisophical note, the three times I've changed source control tools in my career, the engineers have been receptive to re-arranging (refactoring) their code at the same time. It's an excellent time to do it. If they are willing to learn a new tool, then arranging the code in a more sane way is a logical extension of that.

In my experience, code is often laid out in a certain way because of tool limitations. At my last job, if I had imported our code base from PVCS to Perforce in the same exact layout, I'd just have been importing a whole slew of problems to another tool.

I agree that if you're already in SVN and using it, maybe it's not a good idea to re-arrange everything just for this problem, but if one is in the midst of switching from CVS to SVN, I'd seriously consider enforcing a sane code re-arrangement prior to importing the code. Your engineers may be more receptive to the idea than you think.

-Matt

-----Original Message-----
From: news [mailto:news@sea.gmane.org]On Behalf Of Andreas Magnusson
Sent: Thursday, August 18, 2005 1:04 AM
To: users@subversion.tigris.org
Subject: Re: vote: checkout a single file

Phillip Susi wrote:
> I'm not sure what you mean by single file checkout, but the problem you
> describe seems to have a simple solution to me.
>
> Organize your library project so that the source is in one directory and
> the headers and objects go into another directory. Use the svn:external
> attribute to 'attach' the library object and header directory to the
> projects that depend on it. Then when you do a checkout on the other
> projects, you'll get the library with them. If you want the source code
> to the library, you explicitly check out the source directory, which
> presumably you would configure your server to limit access to.

Well, the problem is that not all projects can just rearrange their
file-layouts over night. But might still want to use a better SCM than
for example CVS. On the other hand, I understand that this isn't trivial
to fix in the current WC code.
But once again, understand that most of the projects requesting this
feature, IMHO, cannot afford a rearrangement of their sources. At least
not initially.

Bye,
/Andreas

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

**********************************************************************
E-mail sent through the Internet is not secure. Western Asset therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Western Asset therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail.
**********************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 18 18:08:00 2005

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