[REQUEST 0/1] Requesting your signed-off-by

["Kyle J. McKay" <mackyle@gmail.com>]

Peff,

The tentative patch included in the following [REQUEST 1/1] message includes
so much of your suggested text from:

> From: Jeff King <peff@peff.net>
> Date: July 23, 2013 23:42:59 PDT
> Subject: Re: [PATCH v8 4/4] config: allow http.<url>.* any user matching
> 
[...]
> For (1), I wonder if the explanation would be simpler if the precedences
> of each sub-part were simply laid out. That is, would it be correct to
> say something like:
> 
>  For a config key to match a URL, each element of the config key (if
>  present) is compared to that of the URL, in the following order:
> 
>    1. Protocol (e.g., `https` in `https://example.com/`). This field
>       must match exactly between the config key and the URL.
> 
>    2. Host/domain name (e.g., `example.com` in `https://example.com/`).
>       This field must match exactly between the config key and the URL.
> 
>    3. Path (e.g., `repo.git` in `https://example.com/repo.git`). This
>       field is prefix-matched by slash-delimited path elements, so that
>       config key `foo/` matches URL `foo/bar`. Longer matches take
>       precedence (so `foo/bar`, if it exists, is a better match than
>       just `foo/`).
> 
>    4. Username (e.g., `user` in `https://user@example.com/repo.git`).
> 
>  The list above is ordered by decreasing precedence; a URL that matches
>  a config key's path is preferred to one that matches its username.

that I do not feel comfortable submitting a patch containing it under my name
without your 'Signed-off-by:' as I feel it would be a copyright violation to
do otherwise.  Since the 'Signed-off-by' mechanism is how the Git project
handles this, I'm asking for a reply to the following [REQUEST 1/1] message
that includes the full patch text with a 'Signed-off-by' line added from you
before I include it in any patch series (after which I will add my own
'Signed-off-by' for the other changes I made).

If you would prefer to simply submit your own patch with the changes,
I have no objection and will simply refer to that as a required patch instead.

Thanks,

Kyle


Kyle J. McKay (1):
  docs: update http.<url>.* options documentation

 Documentation/config.txt | 60 +++++++++++++++++++++++++++++-------------------
 1 file changed, 37 insertions(+), 23 deletions(-)

-- 
1.8.3