manifest: tigher manifest parsing and flag use In the manifest line, flags are put directly after the hash, so the parser has been guessing the presence of flags based on the length of the hash. Replace this assumption by an enumeration of the valid flags and removing them from the hash first as they are distinct input values. Consistently handle the expected 256bit length of the SHA1-replacement in the pure Python parser. Check that setting flags will use one of the blessed values. Extend write logic in the C version to handle 256bit hashes as well. Verify that hashes always have exactly the expected length. Since 1070df141718 we should no longer depend on the old extra-byte hack. Differential Revision: https://phab.mercurial-scm.org/D8679

     1

# stack.py - Mercurial functions for stack definition

     2

#

     3

#  Copyright Matt Mackall <mpm@selenic.com> and other

     4

#

     5

# This software may be used and distributed according to the terms of the

     6

# GNU General Public License version 2 or any later version.

     7

     8

from __future__ import absolute_import

     9

    10

    11

def getstack(repo, rev=None):

    12

    """return a sorted smartrev of the stack containing either rev if it is

    13

    not None or the current working directory parent.

    14

    15

    The stack will always contain all drafts changesets which are ancestors to

    16

    the revision and are not merges.

    17

    """

    18

    if rev is None:

    19

        rev = b'.'

    20

    21

    revspec = b'only(%s) and not public() and not ::merge()'

    22

    revisions = repo.revs(revspec, rev)

    23

    revisions.sort()

    24

    return revisions