[REQUEST] Patterns in commit

[James Westby]

On Fri, 2008-02-22 at 13:08 -0500, Forest Bond wrote:
> I think that he is saying that the wildcards aren't working.  Does the Windows
> command prompt support globbing?
> 
> It's possible that things *nix users expect from their shells Windows users
> expect from their applications due to the fact that they have a sub-optimal
> command interpreter.

Indeed, you are exactly right, I was confused by the path
separator used.

Here is an off list reply that I received from QbProg.
(I hope you don't mind me forwarding it, but I don't
know enough to help you myself).

----

Sorry, I used the wrong term "patterns" instead of "wildcards".

Yes, it is possible, but only if you specify each single file in the 
command line. I
would like to use wildcards ( i.e. *.cpp ) instead of single filenames.
Maybe it has something to do with Windows command line, where wildcards 
are not expanded automatically.

However, I can do
bzr add Sources/*.cpp

but not
bzr commit Sources/*.cpp -m".."

i have to do
bzr commit Sources/a.cpp Sources/b.cpp .....

so I suppose that expansion is implemented in "add"?
Another "suggestion": it would be usefoul too to implement an exlude 
list, for example

bzr commit Sources/ --exclude:Sources/NotToBeUpdated.cpp

many times I have to commit an entire directory except one or two
files...

Generally, I think you should use the same input file syntax (like the 
add one?) in every command
that requires a file list.

Thank you
QbProg

----

Looking at the code I see the internal glob expansion is 
only used for add. Please file a bug and we will add it 
to commit as well.

Thanks,

James