cvs2svn -- split multiple projects?

[Bill Moseley <mo...@hank.org>]

I'm wondering if it's possible (or even advisable) to try and split up
a cvs repository when converting to svn.

This cvs repository was just converted to svn:

    From: http://swishe.cvs.sourceforge.net/swishe/
    To:   http://svn.swish-e.org/

Those are separate projects, but cvs2svn converted it all at once.

The projects were originally placed under "trunk" by cvs2svn, but
then they were moved around to make them "top-level" and
trunk/branches/tags are just under swish-e.  That is, looked like this
when first imported:

    http://dev.swish-e.org/browser?rev=1875

The "problem" is that now change sets for different projects are mixed
together.  If I was starting from scratch with svn I probably would
have preferred separate repositories for each project.  For example,
users of swish-e might want to see commit messages for swish-e, but
not for the swish_website.

Of course, there are benefits to having them together if they are
somewhat related.

Anyway, my question is can a single cvs repo be split up when
converting to svn?



-- 
Bill Moseley
moseley@hank.org

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

Re: Checked out files don't preserve file date

[Lorenz <lo...@yahoo.com>]

Eric wrote:
>
>Was it a design intent that when checking out files, the files get 
>changed to today's file date rather than the date that was on them 
>when they were checked in?

yes


>
>This creates large problems (basically, renders impossible for all 
>practical purposes) some other accounting things we are doing with these files.
>
>Is there any way around it?

if you can live with the commit date, then you can set-up the client
in that way.

Lorenz

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

Re: Checked out files don't preserve file date

[Ryan Schmidt <su...@ryandesign.com>]

On Feb 1, 2007, at 11:35, Les Mikesell wrote:

> Eric wrote:
>
>> At 10:18 AM 2/1/2007, Steve Bakke wrote:
>> <SB>>>>>Yes, this was intentional.  Subversion doesn't store the  
>> local modification time upon checkin.  This has come up on the  
>> list recently, and no there isn't any way around it.<<<<<
>> Good morning, Steve.
>> Do you know if CVS did it that way?
>
> CVS sets the timestamp to match the commit time, not the timestamp  
> of the committed file.  But if you check the same thing out twice,  
> the timestamps will match.

And since nobody has mentioned it in this thread, I'll mention it  
now: you can configure Subversion to do the same thing (on checkout  
or update, set the files' dates not to the current time but to the  
commit time). Simply uncomment the line "use-commit-times = yes" in  
the file ~/.subversion/config.


-- 

To reply to the mailing list, please use your mailer's Reply To All  
function


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

Re: Checked out files don't preserve file date

[Les Mikesell <le...@gmail.com>]

Eric wrote:
> At 10:18 AM 2/1/2007, Steve Bakke wrote:
> 
> <SB>>>>>Yes, this was intentional.  Subversion doesn't store the local 
> modification time upon checkin.  This has come up on the list recently, 
> and no there isn't any way around it.<<<<<
> 
> Good morning, Steve.
> 
> Do you know if CVS did it that way?

CVS sets the timestamp to match the commit time, not the timestamp of 
the committed file.  But if you check the same thing out twice, the 
timestamps will match.

-- 
   Les Mikesell
    lesmikesell@gmail.com

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

Re: Checked out files don't preserve file date

[Eric <sp...@scoot.netis.com>]

At 10:18 AM 2/1/2007, Steve Bakke wrote:

<SB>>>>>Yes, this was intentional.  Subversion doesn't store the 
local modification time upon checkin.  This has come up on the list 
recently, and no there isn't any way around it.<<<<<

Good morning, Steve.

Do you know if CVS did it that way?

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

Re: Checked out files don't preserve file date

[Steve Bakke <st...@amd.com>]

Yes, this was intentional.  Subversion doesn't store the local modification
time upon checkin.  This has come up on the list recently, and no there
isn't any way around it.

In my opinion, this one should be high on the list of features to be
considered for 2.0

-Steve


On 2/1/07 9:44 AM, "Eric" <sp...@scoot.netis.com> wrote:

> 
> Was it a design intent that when checking out files, the files get
> changed to today's file date rather than the date that was on them
> when they were checked in?
> 
> This creates large problems (basically, renders impossible for all
> practical purposes) some other accounting things we are doing with these
> files.
> 
> Is there any way around it?
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
> 
> 
> 



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

Checked out files don't preserve file date

[Eric <sp...@scoot.netis.com>]

Was it a design intent that when checking out files, the files get 
changed to today's file date rather than the date that was on them 
when they were checked in?

This creates large problems (basically, renders impossible for all 
practical purposes) some other accounting things we are doing with these files.

Is there any way around it?

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

Re: cvs2svn -- split multiple projects?

[Michael Haggerty <mh...@alum.mit.edu>]

Bill Moseley wrote:
> I'm wondering if it's possible (or even advisable) to try and split up
> a cvs repository when converting to svn.

It is trivial to split up a cvs repo into multiple separate svn
repositories.  Just run cvs2svn multiple times, each time pointing it at
one of the project subdirectories within cvs.

Converting multiple CVS projects into one svn repository, so that each
project has its own trunk/tags/branches, is possible with cvs2svn
version 1.5.x.  Search for "multiproject conversions" in the
documentation and FAQ.  You will need to start the conversion with an
options file to use this feature.

> The "problem" is that now change sets for different projects are mixed
> together.  If I was starting from scratch with svn I probably would
> have preferred separate repositories for each project.  For example,
> users of swish-e might want to see commit messages for swish-e, but
> not for the swish_website.

This can also be configured.  See the documentation near the option
"ctx.cross_project_commits" in the options file.

cvs2svn has its own mailing lists.  You can find them via the cvs2svn
project page,

    http://cvs2svn.tigris.org

Michael

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