clfilter: `bookmark.validdest` should run on unfiltered repo The logic recently added to `bookmark.validdest` uses data about obsolete changesets to see if a bookmark destination is valid. Obsolete changesets are likely to be filtered, so we need to work on an unfiltered repository.

     1

fixbundle() {

     2

    grep -v 'saving bundle' | grep -v 'saved backup' | \

     3

        grep -v added | grep -v adding | \

     4

        grep -v "unable to find 'e' for patching" | \

     5

        grep -v "e: No such file or directory"

     6

}