> 'foo*' removes the whole tree
The more accurate "foo foo/*" should be used instead of "foo*" because
the latter also matches "foobar".
I added the part of these suggestions not related to Files-Excluded to
#688481.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
Package: devscripts
Followup-For: Bug #733111
Hello. I believe that this bug should be reopened.
Having described \* \\ and \?, [1] states that "Any other character
following a backslash is an error.". My understanding is:
- The 'foo\ bar' glob discussed in this bug report is illegal.
- It is no
Hi,
On Thu, Dec 26, 2013 at 09:49:50AM -0800, Russ Allbery wrote:
> Csillag Tamas writes:
>
> > Russ: If you can update the regexp to cover these use case the better.
> > (and thanks for the current one, my Perl knowledge is lacking when it
> > comes to regexpes like this one :)
>
> This change
Csillag Tamas writes:
> Russ: If you can update the regexp to cover these use case the better.
> (and thanks for the current one, my Perl knowledge is lacking when it
> comes to regexpes like this one :)
This change should do it:
> commit d60eb9eb60966d03d8e46e247eaa6f314b6e3555
> Author: CSILL
Hi,
On Wed, Dec 25, 2013 at 09:49:45AM -0800, Russ Allbery wrote:
...
> In order to support file names that contain whitespace, uscan's parsing
> of Files-Excluded needs to handle the character escaping protocol. The
> following code should correctly handle foo\ bar, as well as the other
> more p
Package: devscripts
Version: 2.13.8
Severity: normal
In order to support file names that contain whitespace, uscan's parsing
of Files-Excluded needs to handle the character escaping protocol. The
following code should correctly handle foo\ bar, as well as the other
more pathological cases such as
6 matches
Mail list logo
