rust-index: optimize find_gca_candidates() on less than 8 revisions This is expected to be by far the most common case, given that, e.g., merging involves using it on two revisions. Using a `u8` as support for the bitset obviously divides the amount of RAM needed by 8. To state the obvious, on a repository with 10 million changesets, this spares 70MB. It is also possible that it'd be slightly faster, because it is easier to allocate and provides better cache locality. It is possible that some exhaustive listing of the traits implemented by `u8` and `u64` would avoid the added duplication, but that can be done later and would need a replacement for the `MAX` consts.

     1

# this file holds the definitions that are used in various bzr tests

     2

     3

TERM=dumb; export TERM

     4

echo '[extensions]' >> $HGRCPATH

     5

echo 'convert = ' >> $HGRCPATH

     6

     7

glog()

     8

{

     9

    hg log -G --template '{rev}@{branch} "{desc|firstline}" files+: [{file_adds}], files-: [{file_dels}], files: [{file_mods}]\n' "$@"

    10

}

    11

    12

manifest()

    13

{

    14

    echo "% manifest of $2"

    15

    hg -R $1 manifest -v -r $2

    16

}