CVS commit author being shown as different user than actual committer for mfinkle@mozilla.com

RESOLVED FIXED

Status

mozilla.org
CVS: Administration
RESOLVED FIXED
11 years ago
11 years ago

People

(Reporter: mfinkle, Assigned: justdave)

Tracking

Details

(URL)

Any code that I (mark finkle) check into CVS seems to be tagged as "morgamic%mozilla.com"

I am using the FUEL_DEVEL_BRANCH. You can look at the log of "browser/fuel/src/nsApplication.js" as an example.

To my knowledge, "morgamic" has not touched any of those files.
OS: Mac OS X → All
Hardware: PC → All
Summary: Bad user id → CVS commit author being shown as different user than actual committer for mfinkle@mozilla.com

Updated

11 years ago
Assignee: server-ops → oremj

Updated

11 years ago
Assignee: oremj → server-ops
Assignee: server-ops → justdave
fixed.  when mike.morgan got renamed to morgamic he somehow got a new userid instead of keeping his old one, and his new one matched Mark's.  mike.morgan has now been deleted, and morgamic now has mike.morgan's old uid.

This won't get fixed in bonsai until the next time we do a full repository history rebuild.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
mozilla/browser/fuel has had its history rebuilt, so any checkins in that directory should show up correctly in bonsai queries now.
Dave also did string replacements on the CVS files, which is where the error was at its root, and then rebuilt again, so it should _actually_ be fixed now.
There are now duplicate entries in Bonsai for the FUEL files. Both "morgamic%mozilla.com" and "mark.finkle%gmail.com" are being shown as have committed the same revisions.

http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=&branchtype=match&dir=mozilla%2Fbrowser%2Ffuel&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=all&mindate=&maxdate=&cvsroot=%2Fcvsroot
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
This is a bonsai bug, and without code fixes, will be very hard to fix, and will just happen again next rebuild (and there's probably lots of corruption already because of it).  Bug 375790 filed.  Since I've specified on that bug that we need a way to clean up the existing corruption as part of the fix, I'm restoring the resolution on this one on the assumption that it'll be taken care of on the other.
Status: REOPENED → RESOLVED
Last Resolved: 11 years ago11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.