Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 337508 - Determine which SVN tags we want to keep when we move to git
Summary: Determine which SVN tags we want to keep when we move to git
Status: RESOLVED FIXED
Alias: None
Product: Linux Tools
Classification: Tools
Component: Project (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 0.8.0   Edit
Assignee: Linux Distros Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-17 19:34 EST by Andrew Overholt CLA
Modified: 2011-06-02 18:34 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Overholt CLA 2011-02-17 19:34:15 EST 
http://search.cpan.org/~book/Git-FastExport-0.04/script/git-stitch-repo appended a letter suffix to all tags 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 tags to be 0.6-autotools, etc.
Comment 1 Andrew Overholt CLA 2011-02-22 14:29:43 EST 
Rather than bringing in all the old SVN tags, 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 tags back in later as git tags.
Comment 2 Andrew Overholt CLA 2011-02-23 13:05:30 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 CLA 2011-03-28 12:24:29 EDT 
Time to close?
Comment 4 Andrew Overholt CLA 2011-03-28 13:39:19 EDT 
Yes.  Thanks.  All tags we care about have been merged.