delta/git.git/contrib/contacts, branch ws/curl-http-proxy-over-https

git-contacts: also recognise "Reported-by:"

2017-07-27T16:42:55+00:00

It's nice to cc someone that reported a bug, in order to let them
know that a fix is being considered, and possibly even get their
help in reviewing/testing the patch.

Signed-off-by: Eric Blake 
Signed-off-by: Junio C Hamano

contacts: add a Makefile to generate docs and install

2014-10-15T22:18:27+00:00

Also add a gitignore file for generated files.

Signed-off-by: Sebastian Schuberth 
Signed-off-by: Junio C Hamano

git-contacts: do not fail parsing of good diffs

2014-02-18T23:10:47+00:00

If a line in a patch starts with "--- " it will be deemed
malformed unless it also contains the proper diff header
format. This situation can happen with a valid patch if
it has a line starting with "-- " and that line is removed.

This patch just removes the check in git-contacts.

Signed-off-by: Lars Gullik BjÃ¸nnes 
Signed-off-by: Junio C Hamano

contacts: fix to work in subdirectories

2013-09-18T05:16:22+00:00

Unlike other git commands which work correctly at the top-level or in a
subdirectory, git-contacts fails when invoked in a subdirectory. This is
because it invokes git-blame with pathnames relative to the top-level,
but git-blame interprets the pathnames as relative to the current
directory. Fix this.

Signed-off-by: Eric Sunshine 
Signed-off-by: Junio C Hamano

contacts: reduce git-blame invocations

2013-08-13T16:09:03+00:00

git-contacts invokes git-blame once for each patch hunk it encounters.
No attempt is made to consolidate invocations for multiple hunks
referencing the same file at the same revision. This can become
expensive quickly.

Reduce the number of git-blame invocations by taking advantage of the
ability to specify multiple -L ranges for a single invocation.

Without this patch, on a randomly chosen range of commits:

  % time git-contacts 25fba78d36be6297^..23c339c0f262aad2 >/dev/null
  real  0m6.142s
  user  0m5.429s
  sys   0m0.356s

With this patch:

  % time git-contacts 25fba78d36be6297^..23c339c0f262aad2 >/dev/null
  real  0m2.285s
  user  0m2.093s
  sys   0m0.165s

Signed-off-by: Eric Sunshine 
Signed-off-by: Junio C Hamano

contacts: gather all blame sources prior to invoking git-blame

2013-08-13T16:09:01+00:00

git-contacts invokes git-blame immediately upon encountering a patch
hunk. No attempt is made to consolidate invocations for multiple hunks
referencing the same file at the same revision. This can become
expensive quickly.

Any effort to reduce the number of times git-blame is run will need to
to know in advance which line ranges to blame per file per revision.
Make this information available by collecting all sources as a distinct
step from invoking git-blame.  A subsequent patch will utilize the
information to optimize git-blame invocations.

Signed-off-by: Eric Sunshine 
Signed-off-by: Junio C Hamano

contacts: validate hunk length earlier

2013-08-13T16:08:58+00:00

Rather than calling get_blame() with a zero-length hunk only to have it
rejected immediately, perform hunk-length validation earlier in order to
avoid calling get_blame() unnecessarily.

This is a preparatory step to simplify later patches which reduce the
number of git-blame invocations by collecting together all lines to
blame within a single file at a particular revision. By validating the
blame range early, the subsequent patch can more easily avoid adding
empty ranges at collection time.

Signed-off-by: Eric Sunshine 
Signed-off-by: Junio C Hamano

contrib: contacts: add documentation

2013-07-21T22:15:20+00:00

Assuming that git-contacts may some day be promoted to a core git
command, the documentation is written and formatted as if it already
belongs in Documentation/ even though it presently resides in
contrib/contacts.

Signed-off-by: Eric Sunshine 
Signed-off-by: Junio C Hamano

contrib: contacts: add mailmap support

2013-07-21T22:14:43+00:00

The purpose of git-contacts is to determine a list of people who might
have some interest in a patch or set of changes. It can be used as
git-send-email's --cc-cmd argument or the computed list might be used to
ask for comments on a proposed change.  As such, it is important to
report up-to-date email addresses in the computed list rather than
potentially outdated ones recorded with commits.  Apply git's mailmap
functionality to the retrieved contacts in order to achieve this goal.

Signed-off-by: Eric Sunshine 
Signed-off-by: Junio C Hamano

contrib: contacts: interpret committish akin to format-patch

2013-07-21T22:13:42+00:00

As a convenience, accept the same style  committish as accepted
by git-format-patch. For example:

  % git contacts origin

will consider commits in the current branch built atop 'origin', just as
"git format-patch origin" will format commits built atop 'origin'.

Signed-off-by: Eric Sunshine 
Signed-off-by: Junio C Hamano