mirror of
https://github.com/facebook/sapling.git
synced 2024-10-07 07:17:55 +03:00
9efc7f05e3
Upon pull or unbundle, we display a message with the range of new revisions fetched. This revision range could readily be used after a pull to look out what's new with 'hg log'. The algorithm takes care of filtering "obsolete" revisions that might be present in transaction's "changes" but should not be displayed to the end user.
50 lines
1.3 KiB
Perl
50 lines
1.3 KiB
Perl
Test update.requiredest
|
|
$ cd $TESTTMP
|
|
$ cat >> $HGRCPATH <<EOF
|
|
> [commands]
|
|
> update.requiredest = True
|
|
> EOF
|
|
$ hg init repo
|
|
$ cd repo
|
|
$ echo a >> a
|
|
$ hg commit -qAm aa
|
|
$ hg up
|
|
abort: you must specify a destination
|
|
(for example: hg update ".::")
|
|
[255]
|
|
$ hg up .
|
|
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
|
|
$ HGPLAIN=1 hg up
|
|
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
|
|
$ hg --config commands.update.requiredest=False up
|
|
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
|
|
|
|
$ cd ..
|
|
|
|
Check update.requiredest interaction with pull --update
|
|
$ hg clone repo clone
|
|
updating to branch default
|
|
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
|
|
$ cd repo
|
|
$ echo a >> a
|
|
$ hg commit -qAm aa
|
|
$ cd ../clone
|
|
$ hg pull --update
|
|
abort: update destination required by configuration
|
|
(use hg pull followed by hg update DEST)
|
|
[255]
|
|
|
|
$ cd ..
|
|
|
|
update.requiredest should silent the "hg update" text after pull
|
|
$ hg init repo1
|
|
$ cd repo1
|
|
$ hg pull ../repo
|
|
pulling from ../repo
|
|
requesting all changes
|
|
adding changesets
|
|
adding manifests
|
|
adding file changes
|
|
added 2 changesets with 2 changes to 1 files
|
|
new changesets 8f0162e483d0:048c2cb95949
|