test-patch.t
89 lines
| 2.3 KiB
| text/troff
|
Tads3Lexer
/ tests / test-patch.t
|
r11784 | $ cat > patchtool.py <<EOF | ||
> import sys | ||||
> print 'Using custom patch' | ||||
> if '--binary' in sys.argv: | ||||
> print '--binary found !' | ||||
> EOF | ||||
$ echo "[ui]" >> $HGRCPATH | ||||
$ echo "patch=python ../patchtool.py" >> $HGRCPATH | ||||
$ hg init a | ||||
$ cd a | ||||
$ echo a > a | ||||
$ hg commit -Ama -d '1 0' | ||||
adding a | ||||
$ echo b >> a | ||||
$ hg commit -Amb -d '2 0' | ||||
$ cd .. | ||||
|
r11815 | This test checks that: | ||
- custom patch commands with arguments actually work | ||||
|
r11784 | - patch code does not try to add weird arguments like | ||
--binary when custom patch commands are used. For instance | ||||
--binary is added by default under win32. | ||||
check custom patch options are honored | ||||
$ hg --cwd a export -o ../a.diff tip | ||||
$ hg clone -r 0 a b | ||||
adding changesets | ||||
adding manifests | ||||
adding file changes | ||||
added 1 changesets with 1 changes to 1 files | ||||
updating to branch default | ||||
1 files updated, 0 files merged, 0 files removed, 0 files unresolved | ||||
$ hg --cwd b import -v ../a.diff | ||||
applying ../a.diff | ||||
Using custom patch | ||||
|
r15194 | applied to working directory | ||
|
r12645 | |||
Issue2417: hg import with # comments in description | ||||
Prepare source repo and patch: | ||||
$ rm $HGRCPATH | ||||
$ hg init c | ||||
$ cd c | ||||
|
r14832 | $ printf "a\rc" > a | ||
|
r12645 | $ hg ci -A -m 0 a -d '0 0' | ||
|
r14832 | $ printf "a\rb\rc" > a | ||
|
r12645 | $ cat << eof > log | ||
|
r12728 | > first line which can't start with '# ' | ||
> # second line is a comment but that shouldn't be a problem. | ||||
> A patch marker like this was more problematic even after d7452292f9d3: | ||||
> # HG changeset patch | ||||
> # User lines looks like this - but it _is_ just a comment | ||||
|
r12645 | > eof | ||
$ hg ci -l log -d '0 0' | ||||
$ hg export -o p 1 | ||||
$ cd .. | ||||
Clone and apply patch: | ||||
$ hg clone -r 0 c d | ||||
adding changesets | ||||
adding manifests | ||||
adding file changes | ||||
added 1 changesets with 1 changes to 1 files | ||||
updating to branch default | ||||
1 files updated, 0 files merged, 0 files removed, 0 files unresolved | ||||
$ cd d | ||||
$ hg import ../c/p | ||||
applying ../c/p | ||||
$ hg log -v -r 1 | ||||
|
r14832 | changeset: 1:cd0bde79c428 | ||
|
r12645 | tag: tip | ||
user: test | ||||
date: Thu Jan 01 00:00:00 1970 +0000 | ||||
files: a | ||||
description: | ||||
|
r12728 | first line which can't start with '# ' | ||
# second line is a comment but that shouldn't be a problem. | ||||
A patch marker like this was more problematic even after d7452292f9d3: | ||||
# HG changeset patch | ||||
# User lines looks like this - but it _is_ just a comment | ||||
|
r12645 | |||
$ cd .. | ||||