Micah Cowan wrote:
> Would "hash" really be useful, ever?
Probably not as long as we strip off the hash before we do the comparison.
Tony
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tony Lewis wrote:
> Micah Cowan wrote:
>
>> On expanding current URI acc/rej matches to allow matching against query
>> strings, I've been considering how we might enable/disable this
>> functionality, with an eye toward backwards compatibility.
>
>
Micah Cowan wrote:
> On expanding current URI acc/rej matches to allow matching against query
> strings, I've been considering how we might enable/disable this
> functionality, with an eye toward backwards compatibility.
What about something like --match-type=TYPE (with accepted values of all,
ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I sent the following last month but didn't get any feedback. I'm trying
one more time. :)
- -M
Micah Cowan wrote:
> On expanding current URI acc/rej matches to allow matching against query
> strings, I've been considering how we might enable/disable t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On expanding current URI acc/rej matches to allow matching against query
strings, I've been considering how we might enable/disable this
functionality, with an eye toward backwards compatibility.
It seems to me that one usable approach would be to req
