- In hgfelog.py, the MetaChange detection is too simplistic: a duplicate modification on a second branch shows up as a MetaChange because the file rev on the other branch is re-used. hgsubversion and hgconvert both produce commits from svn merges that have filerevs whose linkrev is not the current commit.
- In FishEye, we create a new revision, but it's parent rev is the last content change revsions parent, instead of the last content change revision, because that's what mercurial stores in it's filectx. We'd have to detect that and cope with it.
- In FE, a subsequent content mod will also have as it's parent the previous content mod revision, instead of the perm change revision, again, because that's what mercurial stores.
- relates to
-
FE-3325 HG: Add basic Mercurial Slurp tests
- Closed
[FE-3101] HG: Cope with MetaChanges (permission changes)
Component/s | New: Indexing [ 41890 ] | |
Component/s | Original: vcs-mercurial [ 13281 ] | |
Labels | Original: hg jac-cleanup-phase1 red | New: hg jac-cleanup-phase1 mercurial red |
Workflow | Original: FE-CRUC Bug Workflow [ 2945068 ] | New: JAC Bug Workflow v3 [ 2957389 ] |
Workflow | Original: FECRU Development Workflow - Triage - Restricted [ 1516409 ] | New: FE-CRUC Bug Workflow [ 2945068 ] |
Fix Version/s | New: N/A [ 54414 ] | |
Resolution | New: Timed out [ 10 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Labels | Original: hg red | New: hg jac-cleanup-phase1 red |
Symptom Severity | New: Minor [ 14432 ] |
Workflow | Original: FECRU Development Workflow - Triage [ 943123 ] | New: FECRU Development Workflow - Triage - Restricted [ 1516409 ] |
Workflow | Original: FECRU Development Workflow (Triage) [ 310067 ] | New: FECRU Development Workflow - Triage [ 943123 ] |
Workflow | Original: Simple review flow with triage [ 210147 ] | New: FECRU Development Workflow (Triage) [ 310067 ] |
Hi everyone,
This issue has been reported several years ago for version older than 3.0.0, which is over 18 major releases behind the latest Fisheye/Crucible version. Additionally, it has not get interest since the time it has been reported. Therefore, we decided to close the issue as Timed Out.
If you still see this bug occurring in the latest release and a fix is very important for you, please don't hesitate to share your feedback in the issue comments. We will continue to watch the issue for further updates.
Cheers
Marek Parfianowicz
Fisheye/Crucible TL