mercurial: on your commits about hash collisions

[Augie Fackler]

Strange. I don’t remember seeing anything in the moderation queue. This user does have nodupes set in mailman, so they won’t get copies of their own messages to the list, but I also don’t see anything on mercurial-devel in April from them.

I’ve got nothing.

> On Apr 30, 2022, at 15:05, Martin von Zweigbergk via Mercurial-devel <mercurial-devel at mercurial-scm.org> wrote:
> 
> 
> Alex says his emails are not getting through to the mailing list. Any idea why? Maybe Augie knows?
> 
> ---------- Forwarded message ---------
> From: Александр Литягин <alexraynepe196 at gmail.com <mailto:alexraynepe196 at gmail.com>>
> Date: Sat, Apr 30, 2022, 06:59
> Subject: mercurial: on your commits about hash collisions
> To: <martinvonz at google.com <mailto:martinvonz at google.com>>
> 
> 
> Hallow Martin!
> 
> You`ve commited into mercurial repo rev 65eda809b943:
> 
> >> tests: demonstrate crash on partial amend with copies in changesets
> 
> Maybe you interests about my patch on similar problems https://bz.mercurial-scm.org/show_bug.cgi?id=6588 <https://bz.mercurial-scm.org/show_bug.cgi?id=6588>
> 
> I got hash duplications when grapht/transplant revisions rigth on same parent. 
> (This problem affects files, not revisions, therefore it not obvious to detect.)
> 
> My solution was to mark duplicate chenges with differ meta tags. And for that, improved file content comparators - it 
> now take into evaluation only data part of change. So now i have full fridom to change contents of changeset meta, with
> no warry that it breaks file change detections in dirstate.
> 
> All patches i placed in bug-report.
> 
> 
> 
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at mercurial-scm.org
> https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-devel/attachments/20220430/24762e1d/attachment-0002.html>