sapling/eden/mononoke/derived_data
Stanislau Hlebik acf26beb79 mononoke: add an option to record committer fields in hg extras
Summary:
When generating hg changesets from git changesets we can run into a situation
where two git commits are almost completely identical with the exception of
committer field. Currently it results in us generating identical mercurial
changesets for different bonsai changesets, and this is something we do not
allow.

Let's do the same thing as hggit does i.e. record committer field in extras if
committer is different from author.

In case of ambiguities (i.e. committer extra is already set, or committer date is set but committer name is not) I opted for returning an error instead of trying to guess what the correct field should be.

Reviewed By: farnz

Differential Revision: D26867740

fbshipit-source-id: 6271e2f7ad421bec296c60ff211723c2162878c6
2021-03-10 23:41:28 -08:00
..
blame vfs: introduce AsyncVfs 2021-03-05 21:47:51 -08:00
changeset_info vfs: introduce AsyncVfs 2021-03-05 21:47:51 -08:00
deleted_files_manifest vfs: introduce AsyncVfs 2021-03-05 21:47:51 -08:00
fastlog vfs: introduce AsyncVfs 2021-03-05 21:47:51 -08:00
filenodes vfs: introduce AsyncVfs 2021-03-05 21:47:51 -08:00
fsnodes vfs: introduce AsyncVfs 2021-03-05 21:47:51 -08:00
mercurial_derived_data mononoke: add an option to record committer fields in hg extras 2021-03-10 23:41:28 -08:00
skeleton_manifest vfs: introduce AsyncVfs 2021-03-05 21:47:51 -08:00
src mononoke: log derivation error to derived data scuba table 2021-03-02 05:38:54 -08:00
test_utils third-party/rust: update futures 2021-03-04 06:42:55 -08:00
unodes vfs: introduce AsyncVfs 2021-03-05 21:47:51 -08:00
utils vfs: introduce AsyncVfs 2021-03-05 21:47:51 -08:00
Cargo.toml vfs: introduce AsyncVfs 2021-03-05 21:47:51 -08:00