Sorry for reacting so late, I didn't read the list carefully in the last weeks
and my gmail filter somehow didn't trigger on that.
On Tuesday 02 October 2012 16:20:22 Junio C Hamano wrote:
> * fa/remote-svn (2012-09-19) 16 commits
> - Add a test script for remote-svn
> - remote-svn: add marks-f
Matthieu Moy writes:
> Andreas Schwab writes:
>
>> Junio C Hamano writes:
>>
>>> When we require "x/**/y", I think we still want it to match "x/y".
>>
>> FWIW, in bash (+extglob), ksh and zsh it doesn't.
>
> You're right about bash, but I see the opposite for zsh and ksh:
>
> zsh$ echo x/**/y
>
On Thu, Oct 04, 2012 at 09:39:02AM -0700, Junio C Hamano wrote:
> Assuming that we do want to match "x/y" with "x/**/y", I suspect
> that "'**' matches anything including a slash" would not give us
> that semantics. Is it something we can easily fix in the wildmatch
> code?
Something like this may
Andreas Schwab writes:
> Junio C Hamano writes:
>
>> When we require "x/**/y", I think we still want it to match "x/y".
>
> FWIW, in bash (+extglob), ksh and zsh it doesn't.
You're right about bash, but I see the opposite for zsh and ksh:
zsh$ echo x/**/y
x/y x/z/y
ksh$ echo x/**/y
x/y x/z/y
Junio C Hamano writes:
> When we require "x/**/y", I think we still want it to match "x/y".
FWIW, in bash (+extglob), ksh and zsh it doesn't.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something compl
Michael Haggerty writes:
> On 10/03/2012 08:17 PM, Junio C Hamano wrote:
>>
>> What is the semantics of ** in the first place? Is it described to
>> a reasonable level of detail in the documentation updates? For
>> example does "**foo" match "afoo", "a/b/foo", "a/bfoo", "a/foo/b",
>> "a/bfoo/c
Stephen Bash writes:
> I seemed to have missed the GSoC wrap up conversation... (links happily
> accepted).
I also seem to have missed such conversation, if anything like that
happened. It certainly would have been nice for the mentors and the
student for each project to give us a two-to-three-
David Michael Barr writes:
> On Wednesday, 3 October 2012 at 9:20 AM, Junio C Hamano wrote:
>>
>> * fa/remote-svn (2012-09-19) 16 commits
>> ...
>>
>> A GSoC project.
>> Waiting for comments from mentors and stakeholders.
>
> I have reviewed this topic and am happy with the design and implemen
On 10/04/2012 01:46 PM, Nguyen Thai Ngoc Duy wrote:
> On Thu, Oct 4, 2012 at 4:34 PM, Michael Haggerty wrote:
>> As for the implementation, it is quite easy to textually convert a glob
>> pattern, including "**" parts, into a regexp.
>
> Or we could introduce regexp syntax as an alternative and l
- Original Message -
> From: "Jonathan Nieder"
> Sent: Thursday, October 4, 2012 4:30:01 AM
> Subject: Re: fa/remote-svn (Re: What's cooking in git.git (Oct 2012, #01;
> Tue, 2))
>
> > > * fa/remote-svn (2012-09-19) 16 commits
> > > - Add
On Thu, Oct 4, 2012 at 4:34 PM, Michael Haggerty wrote:
On Thu, Oct 4, 2012 at 4:34 PM, Michael Haggerty wrote:
> Given that there is no obvious interpretation for what a construct like
> "x**y" would mean, and many plausible guesses (most of which sound
> rather useless), I suggest that we forbi
On 10/03/2012 08:17 PM, Junio C Hamano wrote:
> Nguyen Thai Ngoc Duy writes:
>
>> There's an interesting case: "**foo". According to our rules, that
>> pattern does not contain slashes therefore is basename match. But some
>> might find that confusing because "**" can match slashes,...
>
> By "o
David Michael Barr wrote:
> On Wednesday, 3 October 2012 at 9:20 AM, Junio C Hamano wrote:
>> * fa/remote-svn (2012-09-19) 16 commits
>> - Add a test script for remote-svn
>> - remote-svn: add marks-file regeneration
>> - Add a svnrdump-simulator replaying a dump file for testing
>> - remote-svn:
On Wednesday, 3 October 2012 at 9:20 AM, Junio C Hamano wrote:
>
> * fa/remote-svn (2012-09-19) 16 commits
> - Add a test script for remote-svn
> - remote-svn: add marks-file regeneration
> - Add a svnrdump-simulator replaying a dump file for testing
> - remote-svn: add incremental import
> - re
Nguyen Thai Ngoc Duy writes:
>> I am guessing that the only sensible definition is that "**"
>> requires anything that comes before it (if exists) is at a proper
>> hierarchy boundary, and anything matches it is also at a proper
>> hierarchy boundary, so "x**y" matches "x/a/y"
>
> and "x/y" too?
On Thu, Oct 4, 2012 at 1:17 AM, Junio C Hamano wrote:
> For the double-star at the beginning, you should just turn it into "**/"
> if it is not followed by a slash internally, I think.
>
> What is the semantics of ** in the first place? Is it described to
> a reasonable level of detail in the doc
Nguyen Thai Ngoc Duy writes:
> There's an interesting case: "**foo". According to our rules, that
> pattern does not contain slashes therefore is basename match. But some
> might find that confusing because "**" can match slashes,...
By "our rules", if you mean "if a pattern has slash, it is anc
On Wed, Oct 3, 2012 at 6:20 AM, Junio C Hamano wrote:
> * nd/wildmatch (2012-09-27) 5 commits
> - Support "**" in .gitignore and .gitattributes patterns using wildmatch()
> - Integrate wildmatch to git
> - compat/wildmatch: fix case-insensitive matching
> - compat/wildmatch: remove static vari
18 matches
Mail list logo