My 2 cents, as a LWN "professional hacker": Mercurial planning to transition away from SHA-1

-

 

LWN article:

Mercurial planning to transition away from SHA-1
https://lwn.net/Articles/832111/

My comment:

https://lwn.net/Articles/833425/

Content of my comment:

My 2 cents, as a LWN "professional hacker":

Existing Mercurial users are using Mercurial with existing old-and-aging Mercurial repositories that use SHA-1.
At my job, we use Mercurial, because it is what it is.
Unless an existing repository can have both old SHA-1 hashes and $NEW-HASH hashes at the same time, I don't think that this is going to be a thing. Users just don't care.

Branching

You can think of Mercurial branches as Commit Namespaces rather than true branches as intended by CVS, Subversion, Git and really computer science in general. In Mercurial, each commit belongs to a Mercurial branch explicitly and forever. (The information of branch name is encoded in the data of a commit.) In Git, a commit does not contain in its data the branch name.

So, what did Mercurial do to fix that, in order to add standard branching semantics to replace "Mercurial Branches" ?
Bookmarks !

In Mercurial, bookmarks are basically Git branches. (A temporary label on a commit, that will advance as you add commits on top.) In Mercurial, most commands (push, pull, export, ...) support "bookmarks". You can do "hg push origin -B topic", which is equivalent to "git push origin topic". But, "hg log" does not have the -B switch for bookmarks.

In August 2020, I submitted patches to add bookmark support in the "hg log" command.
The patch https://phab.mercurial-scm.org/D8973 has been approved.
But, I have not seen it land in the maintainer's repo at https://www.mercurial-scm.org/repo/hg or even at https://www.mercurial-scm.org/repo/hg-committed/ ...

I was a bit disappointed. Was my patch series silently put to rest, behind the curtain ?

Deduplication

Mercurial has a fancy format called "Bundle" for the wire protocol. But, the .hg/store does not use "Bundle", and the result is that if you add 10 files with the same content to a Mercurial repository, the Mercurial object store will have 10 copies of it. There is no deduplication. Git has deduplication (since day one) which does the right thing of not storing 10 objects with the same content. Linus Torvalds calls that a content-addressable store.

Conclusion

To me, Mercurial is a dinosaur software. It does not evolve, and is going extinct.

At least, the third DVCS, Fossil, acknowledges what it wants to be in its name !

Comments

Post a Comment

Popular posts from this blog

A survey of the burgeoning industry of cloud genomics

-
Image
I like lists. Here is a list of companies in the cloud genomics industry. Table 1: Companies acting in the industry of cloud genomics. The list is in no particular order. Company Products People Founded Link GenoSpace, LLC - GenoSpace platform - John Quackenbush (CEO) 2011 https://www.genospace.com/ DNAnexus, Inc. - DNAnexus Platform - DNAnexus Platform SDK (a.k.a. dx-toolkit) - Serafim Batzoglou (co-founder) - Andreas Sundquist (co-founder and CTO) - a bunch of other famous people in the field 2009 https://dnanexus.com/ Seven Bridges Genomics, Inc. - IGOR - IGOR Python SDK - Igor Bogicevic (CTO) 2009 https://www.sbgenomics.com/ BGI - EasyGenomics - Xing Xu (Senior Product Manager) Introduced in 2012 https://www.easygenomics.com/ Illumina, Inc. - BaseSpace™ - BaseSpace API - Alex Dickinson (SVP of Cloud Genomics) Introduced in 2011 https://basespace.illumina.com/ Era7 Information Technologies SLU - BG7...
Read more

Generating neural machine instructions for multi-head attention

-
  An animal can do training and inference every day of its existence until the day of its death. A forward pass is all you need.   Here is the current model configuration that I use for multi-head attention:         let sequence_length = 6;         let vocab_size = 20;         let n_embd = 64;         let num_heads = 8; You can see the full model here: https://github.com/sebhtml/novigrad/blob/8df6192829edd9cda3a221e12affa770fbda2a1b/src/models/mega_man_attention.rs The struct uses Embedding, MultiHeadAttention, Linear, Softmax: struct MegaManAttentionModel {     input_shape: Vec<usize>,     output_shape: Vec<usize>,     vocab_size: usize,     sequence_length: usize,     embedding: Embedding,     multi_head_attention: MultiHeadAttention, ...
Read more

Adding ZVOL VIRTIO disks to a guest running on a host with the FreeBSD BHYVE hypervisor

-
On atlantis.domain (my FreeBSD BHYVE hypervisor host), I use these commands: Install FreeBSD on a 10G disk. vm create -s 10G guestname   vm install FreeBSD-12.1-RELEASE-amd64-memstick.img vm console guestname Add 8 30GB zvol-based disks vm add -d disk -t zvol -s 30G guestname vm add -d disk -t zvol -s 30G guestname vm add -d disk -t zvol -s 30G guestname vm add -d disk -t zvol -s 30G guestname vm add -d disk -t zvol -s 30G guestname vm add -d disk -t zvol -s 30G guestname vm add -d disk -t zvol -s 30G guestname vm add -d disk -t zvol -s 30G guestname You will need to do vm poweroff guestname vm start guestname because the guest does not seem to see the 8 30GB without power cycling. (rebooting won't work) *** If you want the boot disk (the one create by "vm create") to be a zvol, you must edit the template: root@atlantis:~ # zfs snapshot tank/vm-bhyve@2020-06-11-2145 root@atlantis:~ # mount -t zfs tank/vm-bhyve@2020-06-11-2145 /tank/vm-bhyve@2020-06-11-2145 r...
Read more