[issue2853] strange behaviour of -I/--include option
Christian Ebert
bugs at mercurial.selenic.com
Tue Jun 14 18:07:34 UTC 2011
New submission from Christian Ebert <blacktrash at gmx.net>:
So far I haven't come up with a simpler test case, but here comes what
happens in a "real world" repo:
$ cd flowplayer/
$ touch test/issue100.html
$ touch dev/issue100.html
$ hg add -I'*/issue100.html'
adding dev/issue100.html
$ hg add dev/issue100.html
flowplayer/dev/issue100.html already tracked!
$ hg add test/issue100.html
$ hg ci -m 'add -I issue' -I'*/issue100.html'
$ hg tip -v
changeset: 2818:fe0207397121
tag: tip
user: Christian Ebert <blacktrash at gmx.net>
date: Tue Jun 14 19:52:53 2011 +0200
files: flowplayer/dev/issue100.html flowplayer/test/issue100.html
description:
add -I issue
$ hg rollback
repository tip rolled back to revision 2817 (undo commit)
working directory now based on revision 2817
$ hg st -mard
M flowplayer/openx.html
M flowplayer/test/issue296.html
M flowplayer/test/issue299.html
M flowplayer/test/minimal.html
A flowplayer/dev/issue100.html
A flowplayer/test/issue100.html
$ hg forget -I'*/issue100.html'
abort: no files specified
$ hg forget test/issue100.html dev/issue100.html
To me this looks like the -I option sometimes works, and sometimes it
doesn't. But I am utterly at a loss as to why. Only commit works as I would
expect.
----------
messages: 16510
nosy: blacktrash
priority: bug
status: unread
title: strange behaviour of -I/--include option
____________________________________________________
Mercurial issue tracker <bugs at mercurial.selenic.com>
<http://mercurial.selenic.com/bts/issue2853>
____________________________________________________
More information about the Mercurial-devel
mailing list