From: Dave Borowitz <dborowitz@google.com>
To: git@vger.kernel.org, gitster@pobox.com
Cc: Dave Borowitz <dborowitz@google.com>
Subject: [PATCH v2 0/9] Flags and config to sign pushes by default
Date: Wed, 19 Aug 2015 11:26:38 -0400 [thread overview]
Message-ID: <1439998007-28719-1-git-send-email-dborowitz@google.com> (raw)
Changes since v1:
- Rebased on 44e02239
- Use options --[no-]signed|--signed=(yes|no|if-asked)
- Support general yes/true/1/etc. option parsing.
- Convert builtin/send-pack.c to use option parsing API for better code
reuse.
- Various cleanups as suggested by Junio.
v1 can be found at:
http://thread.gmane.org/gmane.comp.version-control.git/275881
Dave Borowitz (9):
Documentation/git-push.txt: Document when --signed may fail
Documentation/git-send-pack.txt: Flow long synopsis line
Documentation/git-send-pack.txt: Document --signed
gitremote-helpers.txt: Document pushcert option
transport: Remove git_transport_options.push_cert
config.c: Expose git_parse_maybe_bool
builtin/send-pack.c: Use option parsing API
Support signing pushes iff the server supports it
Add a config option push.gpgSign for default signed pushes
Documentation/config.txt | 8 ++
Documentation/git-push.txt | 15 ++-
Documentation/git-send-pack.txt | 16 ++-
Documentation/gitremote-helpers.txt | 3 +
builtin/push.c | 42 +++++++-
builtin/send-pack.c | 192 ++++++++++++++++--------------------
cache.h | 1 +
config.c | 6 +-
remote-curl.c | 16 ++-
send-pack.c | 43 ++++++--
send-pack.h | 12 ++-
transport-helper.c | 34 +++----
transport.c | 11 ++-
transport.h | 6 +-
14 files changed, 253 insertions(+), 152 deletions(-)
--
2.5.0.276.gf5e568e
next reply other threads:[~2015-08-19 15:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 15:26 Dave Borowitz [this message]
2015-08-19 15:26 ` [PATCH v2 1/9] Documentation/git-push.txt: Document when --signed may fail Dave Borowitz
2015-08-19 15:26 ` [PATCH v2 2/9] Documentation/git-send-pack.txt: Flow long synopsis line Dave Borowitz
2015-08-19 19:56 ` Junio C Hamano
2015-08-19 19:59 ` Dave Borowitz
2015-08-19 20:10 ` Junio C Hamano
2015-09-11 16:22 ` Junio C Hamano
2015-08-19 15:26 ` [PATCH v2 3/9] Documentation/git-send-pack.txt: Document --signed Dave Borowitz
2015-08-19 15:26 ` [PATCH v2 4/9] gitremote-helpers.txt: Document pushcert option Dave Borowitz
2015-08-19 15:26 ` [PATCH v2 5/9] transport: Remove git_transport_options.push_cert Dave Borowitz
2015-08-19 15:26 ` [PATCH v2 6/9] config.c: Expose git_parse_maybe_bool Dave Borowitz
2015-08-19 15:26 ` [PATCH v2 7/9] builtin/send-pack.c: Use option parsing API Dave Borowitz
2015-08-19 18:00 ` Stefan Beller
2015-08-19 19:46 ` Dave Borowitz
2015-08-21 15:06 ` Jeff King
2015-08-19 15:26 ` [PATCH v2 8/9] Support signing pushes iff the server supports it Dave Borowitz
2015-08-19 19:58 ` Junio C Hamano
2015-08-19 20:00 ` Dave Borowitz
2015-08-19 15:26 ` [PATCH v2 9/9] Add a config option push.gpgSign for default signed pushes Dave Borowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1439998007-28719-1-git-send-email-dborowitz@google.com \
--to=dborowitz@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).