|
Yeah, so shouldn't the root of org.eclipse.higgins hold three directories?:
branches
tags
trunk
Is it as simple as creating the trunk directory and moving everything into it?
>>> Michael McIntosh <mikemci@xxxxxxxxxx> 11/22/07 10:46 AM >>>
It sounds like our SVN conversion has violated some previously unknown
best practice.
It looks like we may need to more our repo.
Regards,
Mike
----- Forwarded by Michael McIntosh/Watson/IBM on 11/22/2007 12:44 PM
-----
Thomas Hallgren <thomas@xxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
11/22/2007 11:43 AM
Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
To
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
cc
Subject
[cross-project-issues-dev] I see weird things happening in our SVN repo
Hi,
Over the last couple of days the number of revisions in our SVN
repository nearly doubled. Looking at the repository I find branches and
tags directly under the /svnroot (they seem to belong to the
org.eclipse.higgins project). Having branches and tags directly under
the /svnroot means that all projects share the same set of branches and
tags. IMHO, that's bad practice.
Most projects have the standard structure, i.e.
/svnroot/org.eclipse.xxxx/
trunk/
tags/
branches/
I think we need to make this the standard for all projects. The sooner
the better. The projects that deviate from the standard are:
org.eclipse.higgins
org.eclipse.linuxtools
org.eclipse.spaces
Does anyone have a different opinion about this?
Regards,
Thomas Hallgren
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
higgins-dev mailing list
higgins-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/higgins-dev
|
