On Mon, Nov 12, 2007 at 03:51:22PM +0100, Erik Huelsmann wrote:
> Hi Rodrigo!
> > ------- Additional comments from firstname.lastname@example.org Mon Nov 12 05:44:01 -0800 2007 -------
> > I'm goint to implement this functionality for a client,
> That's great! If you could share a description of the approach you're
> going to use - maybe posting some half-way progress on dev@ - we could
> help you improve the quality of your code and even help improve
> chances the code will be included in the main line.
I don't yet have something to show, but will post it as soon as I can.
What's the reason Garrett Rooney's patch was never integrated? I'll be
taking a look a it, too, and steal what I can :)
I saw in that thread that there was a question about recursive use. If
I understood the objection, the problem is how to resolve a pattern
such as */tags. My answer to that will be to completely punt the
issue, and only allow absolute paths to have wildcards.
Another issue that must be solved is that several entries can apply to
the same path. I propose the following rules in order to disambiguate:
- Repo specific trumps pan-repo
- More path components trump less
- Less wildcards trump more
Do these seem reasonable? Any comments?
GPG-Fingerprint: 7C81 E60C 442E 8FBC D975 2F49 0199 8318 ADC9 BC28
Received on Tue Nov 13 23:56:10 2007