[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Proposal: Subversion Migration

From: Adam Fedor
Subject: RE: Proposal: Subversion Migration
Date: Tue, 25 Oct 2005 08:48:22 -0400

> -----Original Message-----
> From: Andrew Ruder [mailto:address@hidden
> automatically.  For example, I can make a /modules/dev-apps that
> basically says:
> Check out /apps/gorm/trunk into the gorm directory
> Check out /apps/easydiff/trunk into the easydiff directory
> and so on.  When you do an svn update, or a commit or 
> anything, it will
> commit to the actual location in the repository.  svn:externals are a
> powerful thing when used in this regard...

Yes, after looking at it a bit, I think have a separate repository for each 
independant 'package' would be good.

> Interesting, I did not realize that 
> non-fsf-copyright-assigned projects
> existed in the GNUstep CVS.  Perhaps to save the confusion we 
> should set
> up another project for the nonfsf stuff.  The modules I refer to above
> can reference external svn repository locations every bit as 
> easily, so
> we could still make dev-libs pull in from the non-fsf place.  But when
> setting up commit access we'd have the advantage that anyone 
> getting the
> fsf gnustep commit access would need to have signed the 
> forms, etc.. to
> assign copyright on code placed in that repository.
> Having such a project may also be an excellent place for 
> people to host
> non-fsf-copyright-assigned projects directly related to gnustep.

Yep. A few got in before I was thinking about how the repository should be 
organized. A non-fsf place sounds like a good idea. 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]