| commit | f5da077b1f9e28a473f8219d8b8391450b794abf | |
| author | Jeff King <peff@peff.net> | |
| Mon, 20 Nov 2017 19:18:46 +0000 (20 14:18 -0500) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 21 Nov 2017 02:01:02 +0000 (21 11:01 +0900) | ||
| tree | 825ad551071f0206eedf696aa31081b82031f03b | treesnapshot (tar.gz zip) |
| parent | 007d06aa57e673c95da583d2afa30bb14fb69e28 | commitdiff |
git-jump: give contact instructions in the README
Let's make it clear how patches should flow into
contrib/git-jump. The normal Git maintainer does not
necessarily care about things in contrib/, and authors of
individual components should be the ones giving the final
review/ack for a patch. Ditto for bug reports, which are
likely to get more attention from the area expert.
Signed-off-by: Jeff King <peff@peff.net>
Reviewed-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Let's make it clear how patches should flow into
contrib/git-jump. The normal Git maintainer does not
necessarily care about things in contrib/, and authors of
individual components should be the ones giving the final
review/ack for a patch. Ditto for bug reports, which are
likely to get more attention from the area expert.
Signed-off-by: Jeff King <peff@peff.net>
Reviewed-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| contrib/git-jump/README | diffblobblamehistory |