Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • hg-git-test-migration hg-git-test-migration
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 79
    • Issues 79
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 11
    • Merge requests 11
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • heptapod
  • Testing Projects
  • hg-git-test-migrationhg-git-test-migration
  • Issues
  • #134

Closed
Open
Created Nov 24, 2014 by Georges Racinet@gracinet🦑Owner

Some forms of authors don't round-trip

Created originally on Bitbucket by glandium (Mike Hommey)

See the following reduced testcase:

#!shell

$ mkdir a b
$ cd b
$ git init --bare
$ cd ../a
$ hg init
$ echo a > a
$ hg commit -A -m a -u foo@bar
$ hg push ../b
$ cd ..
$ hg clone b c

The changeset in c doesn't have the same sha1 as the one in a because the author changed from foo@bar to foo@bar <foo@bar>. Reading the code, there are likely other forms that don't round-trip.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking