Definitely what I would expect -- include lists are intended for retrieving
existing files, not creating new ones.
What's happening is that TOUCH is looking for the file "one", can't find it,
and then looks for the file "two". It can't find that one either, so then
it checks to see if you're trying to create a file, and it duly creates
"two". The "one" is long gone, and indeed never even seen by TOUCH as it
was eaten by the "find file" routine.
But since you can simply remove the ; to get the desired result, it's not
much of a loss ...
I understand what you're saying about the include list and file creation,
but the way I always use the include list is when I have a folder with
several files, like trying to create one and two in folder:
touch /c folder\one;two
In this case, removing the semicolon creates folder\one and two, but two is
now in the wrong place.
Since the include list is clearly designed for existing files, perhaps an
additional note with touch /c to indicate that neither wildcards nor include
lists may be used would be sufficient.
2010 Sundays: 4/4, 6/6, 8/8, 10/10, 12/12 and 5/9, 9/5, 7/11, 11/7.
Next year they're Monday.