Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 337507

Summary:	Determine which SVN branches we want to keep when we move to git
Product:	[Tools] Linux Tools	Reporter:	Andrew Overholt <overholt>
Component:	Project	Assignee:	Linux Distros Inbox <linux.distros-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	akurtakov
Version:	unspecified
Target Milestone:	0.8.0
Hardware:	PC
OS:	Linux
Whiteboard:

Description Andrew Overholt

2011-02-17 19:34:10 EST

http://search.cpan.org/~book/Git-FastExport-0.04/script/git-stitch-repo appended a letter suffix to all branches that were named the same across our various SVN repositories.  For example, in the merged repository we ended up with 0.6-A, 0.6-B, etc.  We'll need to go through and rename the branches to be 0.6-autotools, etc.

Comment 1 Andrew Overholt

2011-02-22 14:28:36 EST

Rather than bringing in all these old branches, I'm going to consult with the committers to determine which we should mirror in git and which should be dropped.  Stay tuned for a list.

I'm also removing this as a blocker for moving to git since we can always add any SVN branches back in later as git branches.

Comment 2 Andrew Overholt

2011-02-23 13:05:14 EST

Emails have been sent to committers requesting input on any branches or tags that should be brought over to the git repo.

Comment 3 Alexander Kurtakov

2011-03-28 12:24:38 EDT

Time to close?

Comment 4 Andrew Overholt

2011-03-28 13:39:11 EDT

Yes.  Thanks.  All branches we care about have been merged.