Uploaded image for project: 'FishEye'
  1. FishEye
  2. FE-3101

HG: Cope with MetaChanges (permission changes)

    XMLWordPrintable

    Details

      Description

      1. 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.
      2. 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.
      3. 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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              Anonymous
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Time Spent - 1h Remaining Estimate - 8h
                  8h
                  Logged:
                  Time Spent - 1h Remaining Estimate - 8h
                  1h