On Fri, Mar 03, 2006 at 07:28:34PM -0500, Duncan Murdoch wrote:
> Steve Kargl wrote:
> >On Fri, Mar 03, 2006 at 05:30:05PM -0500, Frank Gruman wrote:
> >>Steve Kargl wrote:
> >>>On Fri, Mar 03, 2006 at 10:53:15PM +0100, Ryan Schmidt wrote:
> >>>>export S=$HOME/path/to/SVN
> >>>>mkdir $S
> >>>>svnadmin create $S/A
> >>>>cd $HOME/prj
> >>>>svn checkout $S/A
> >>>Having to explicitly give an environmental variable on the
> >>>command line for each svn command, kind of defeats the whole
> >>>purpose of such variables.
> >>I disagree. You could theoretically have different variables pointing
> >>to different repositories with various working copies on your computer.
> >>For example - I have 3 separate working copies attached to 3 separate
> >>repositories. The first is our code server, the second is a completely
> >>separate repository for documents, and the third is my own personal code
> >>server that I have hosted from home. SO - in the CVS world, what would
> >>I set my CVSROOT to? Given Ryan's response, I could create
> >>$CODE/project/path, $DOCS/project/path, and $HOME/project/path.
> >It is clear that you and I have a different idea on what a repository
> >is. To me, a repository contains independent projects. To you, each
> >independent project has its own repository.
> Or perhaps he collaborates on several projects hosted by other people.
So, you're suggesting that I don't collaborate with others?
I have CVSROOT set to $HOME/CVS and I had three different
versions of GCC on my system via cvs. GCC moved to svn,
which has prompted my potential move of $HOME/CVS to svn.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sat Mar 4 04:08:38 2006