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

Bug 360865

Summary:	Support alternate format used by Buckminster project for committer ids
Product:	[Technology] Dash	Reporter:	Wayne Beaton <wayne.beaton>
Component:	Commits Explorer (Retired)	Assignee:	Project Dash Incoming bugs <dash-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	thomas
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug

Description Wayne Beaton

2011-10-13 12:20:52 EDT

Some commits in the Buckminster project's Git repository have author/committer fields in the following form:

Commit:     thallgren <thallgren@ee007c2a-0a25-0410-9ab9-bf268980928c>
Author:     mruzicka <mruzicka@ee007c2a-0a25-0410-9ab9-bf268980928c>

These are not currently mapping to a committer.

I assume that the part following the @ is a UUID that is somehow meaningful to the project.

Since the value in the braces is not a valid email address, it should be relatively easy to detect that and grab either the chars ahead of the @ or the name preceding the braces.

Comment 1 Thomas Hallgren

2011-10-13 16:33:06 EDT

I think those entries stem from the conversion from SVN. The UUID's were not invented by us and have no meaning that I'm aware of. Is this a problem? What can we do to fix it?

Comment 2 Wayne Beaton

2011-10-14 10:31:15 EDT

I'm pretty sure that I can consistently extract and map the committer id from the fields as specified. I don't think you need to do anything. Unless you have an issue with it.

Comment 3 Thomas Hallgren

2011-10-14 12:37:09 EDT

Absolutely no issue from my end :-)

Comment 4 Eclipse Genie

2014-04-26 16:27:50 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 5 Eclipse Genie

2016-04-16 13:10:26 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 6 Wayne Beaton

2016-04-18 10:18:04 EDT

As I encounter these, I modify the corresponding committer record to treat the form as an alternative email address. I haven't run into one of these for a long time. I think that we can declare victory.