subrepo: avoids empty commit when .hgsubstate is dirty (issue2403) This patch avoids empty commit when .hgsubstate is dirty. Empty commit was caused by .hgsubstate being updated back to the state of the working copy parent when committing, if a user had changed it manually and not made any changes in subrepositories. The subrepository state from the working copies parent is compared with the state calculated as a result of trying to commit the subrepositories. If the two states are the same, then return None otherwise the commit is just done. The line: "committing subrepository x" will be written if there is nothing committed, but .hgsubstate is dirty for x subrepository.

progress: don't compute estimate without a total Without this, computing an estimate crashes. Test included.

subrepo: use low-level git-diff-index for dirty() Despite its name, git-diff-index compares a revision to the files in the working directory. This seems way less sketchy and more future proof than parsing human-readable git-status.

subrepo: defer determination of git's current branch

subrepo: incorporate tracking branches into gitbranchmap

subrepo: use low-level git-for-each-ref command in branchmap This command's output doesn't change across versions, and it also disambiguates cases where there are slashes in local branch names.

progress using tests: disable time estimates to avoid flakiness

progress: include time estimate as part of the default progress format

progress: only show time estimate when progress format contains 'estimate'

progress: fix adding format elements after the progress bar Prior to this change, format elements after the progress bar would show up in the wrong order.

test-progress: test completion estimates and progress bar delay

subrepo: add progress bar support to archive

archive: add support for progress extension

progress: test setting progress.width This also makes the tests readable in a 80-character terminal which is why I made the change to both tests.

tests: add filtercr.py helper for progress tests The two tests that used filtercr.py already used a slightly different version, which explains why test-convert-svn-move.t changed after switching to using $TESTDIR/filtercr.py.

test-archive: whitespace cleanup

progress: explain format strings to translators

subrepo: re-backout 2245fcd0e160, remove test 7397a53219c9 re-removed the bad fix but not the test.

subrepo: re-backout 2245fcd0e160 This bug got introduced into default simultaneously with its backout, so future merges didn't eradicate it.

merge with stable

tag: abort if not at a branch head (issue2552) Since it's usually only desirable to make tag commits on top of branch heads, abort if the working dir parent is not a branch head. -f/--force may be passed to commit at a non-head anyway. Does not abort if working dir parent is a named branch head but not a topological head.

tag: fix uncommitted merge check and error message (issue2542) This patch corrects the check for tagging on an uncommitted merge. We should never commit a new tag changeset on an uncommitted merge, whether or not --rev is specified. It also changes the error message from: abort: cannot partially commit a merge (do not specify files or patterns) to the much more accurate (and terse): abort: uncommitted merge Local tags are ok.

tag: don't check .hgtags status if --local passed Local tags don't create a commit, so we don't need to check the status of .hgtags.

progress: refactor for readability and show XXs instead of 0mXXs.

progress: Add estimated time remaining for long tasks Output looks roughly like this: updating [======================> ] 1547/4842 0m13s output will either show h:m or m:s

progress: react more reasonably to nested progress topics Previously, we'd reset the entire progress bar state when a topic was completed, even if it wasn't the outermost progress topic. Now we print the state of the next progress topic on the stack if one is left rather than reset the progress bar.

Merge with stable

util: work around behavior change in Python 2.7.1

merge with stable

merge default heads in crew and main

merge stable heads in crew and main

eol: improve help on whether EOLs are changed in working copy or repository Improved help to make it more clear for users which changes are only changes in the working copy and which changes that will go into the repository (on the following commit). Futhermore a note on when the rules will be applied to the working directory.