view tests/test-mq-qclone-http.out @ 11063:eb23c876c111

tag: warn users about tag/branch possible name conflicts As reported recently, Mercurial users can easily find confusion when using a common name for a tag and a branch. It seems reasonable to warn them about this potential outcome, to avoid that "surprise". * Explain briefly the issue in "hg help tag" * Warn when tagging a revision
author Nicolas Dumazet <nicdumz.commits@gmail.com>
date Mon, 19 Apr 2010 17:41:12 +0900
parents 662b0f9eb148
children
line wrap: on
line source

adding a
adding b
[mq]: b.patch
a
b.patch
% test with recursive collection
200 Script output follows


/a/
/a/.hg/patches/

requesting all changes
adding changesets
adding manifests
adding file changes
added 2 changesets with 2 changes to 2 files
requesting all changes
adding changesets
adding manifests
adding file changes
added 1 changesets with 3 changes to 3 files
updating to branch default
3 files updated, 0 files merged, 0 files removed, 0 files unresolved
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
a
applying b.patch
now at: b.patch
imported patch b.patch
a
% test with normal collection
200 Script output follows


/a/
/a/.hg/patches/

requesting all changes
adding changesets
adding manifests
adding file changes
added 2 changesets with 2 changes to 2 files
requesting all changes
adding changesets
adding manifests
adding file changes
added 1 changesets with 3 changes to 3 files
updating to branch default
3 files updated, 0 files merged, 0 files removed, 0 files unresolved
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
a
applying b.patch
now at: b.patch
imported patch b.patch
a
% test with old-style collection
200 Script output follows


/a/
/a/.hg/patches/

requesting all changes
adding changesets
adding manifests
adding file changes
added 2 changesets with 2 changes to 2 files
requesting all changes
adding changesets
adding manifests
adding file changes
added 1 changesets with 3 changes to 3 files
updating to branch default
3 files updated, 0 files merged, 0 files removed, 0 files unresolved
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
a
applying b.patch
now at: b.patch
imported patch b.patch
a
% test --mq works and uses correct repository config
comparing with http://localhost:$HGPORT2/a/.hg/patches
searching for changes
no changes found
0 b.patch