I'd like to second Garrett's suggestion. I would be extremely
interested in reading these approaches and learning from them. Thanks.
Maggie
Respectfully,
Maggie Tompkins
Configuration Management
Integrated Applications Division
Technology Services Organization
Programs and Resources Department
Headquarters United States Marine Corps
816-926-1117 (DSN 465); Margaret.Tompkins@dfas.mil
-----Original Message-----
From: Garrett McGrath [mailto:gmcgrath@Princeton.EDU]
Sent: Tuesday, December 19, 2006 9:03 AM
To: users@subversion.tigris.org
Subject: RE: Making a branch
There seems to have been a lot of similar issues recently with people
using svn and what would be considered unconventional project layouts.
Would it be possible for one (or preferrably two or three) people to
write up some different angles of approach for using svn with different
project enviroments, sort of a 'recommend practices in software
engineering'? What I'm thinking of isn't really a mailing list note,
but a well thought out article of best practices for a specific setup of
project file storage and the use of svn with that style of project.
This could relieve a lot of the issues we've seen recently with people
trying to do things that appear (on the surface) to be outside the box
svn but could be solved thru some solid planning. Just a thought.
-Garrett
-----Original Message-----
From: Steve.Nelson@uk.delarue.com [mailto:Steve.Nelson@uk.delarue.com]
Sent: Tuesday, December 19, 2006 9:55 AM
To: Chris.Fouts@qimonda.com; users@subversion.tigris.org
Subject: RE: Making a branch
> From: Chris.Fouts@qimonda.com [mailto:Chris.Fouts@qimonda.com]
> >It isn't convenient/possible to have subdirectories per program in
> >trunk, or even functional groupings, so when a ticket is raised
> >requesting changes to be made to, eg, half a dozen programs in trunk,
> (snip)
>
> Can't you do a
> > svn cp //repos/trunk/dir //repos/branch/issue#
The problem is that there are no directories under trunk - just several
hundred programs. This is because there's no way to organise them
clearly - they represent one project, and they have different functions,
but they just exist as an amorophous mass of code. Directories only
make sense for specific issues which require changes to a given set of
code.
I've just managed to do a "create folder" operation using the repository
browser in tortoisesvn, but I don't know what that actually did on the
command line. Anyone?
S.
**********************************************************************
This e-mail and any files attached are strictly confidential, may be
legally privileged
and are intended solely for the addressee. If you are not the intended
recipient, note
that any disclosure, copying, distribution, or use of the contents of
this
message and
attachments is strictly prohibited. Please notify the sender immediately
by
return email,
phone or fax and then delete the e-mail and any attachments immediately.
The
views
and or opinions expressed in this e-mail are not necessarily the views
of De
La Rue plc
or any of its subsidiaries and the De La Rue Group of companies, their
directors,
officers and employees make no representation about and accept no
liability
for its
accuracy or completeness. Please ensure you have adequate virus
protection
before
you open any attachment as the De La Rue Group of companies do not
accept
liability
for any viruses.
---------------------------------------------------------------------
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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 19 18:45:37 2006