From: Ted Ts'o <tytso@mit.edu>
To: Junio C Hamano <gitster@pobox.com>
Cc: Sverre Rabbelier <srabbelier@gmail.com>,
git@vger.kernel.org, Jeff King <peff@peff.net>,
"Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: [PATCH v3 0/4] Signed push
Date: Sat, 10 Sep 2011 15:22:25 -0400 [thread overview]
Message-ID: <20110910192225.GA5397@thunk.org> (raw)
In-Reply-To: <7vehzopdga.fsf@alter.siamese.dyndns.org>
On Sat, Sep 10, 2011 at 09:30:29AM -0700, Junio C Hamano wrote:
> Sverre Rabbelier <srabbelier@gmail.com> writes:
>
> > I think this is also some further motivation to have a
>
> Did you miss that I already mentioned that workaround? It does not _fix_
> the fundamental breakage, which is that you are _forcing_ the sending side
> to keep copies, though.
I guess I'm confused about what the problem is with this?
If I do something like this:
git tag -s -m for_linus-20110910 for_linus-20110910
git push github
git push --tags github
I'm "forcing" the sending side to keep the signed tag, no? Isn't that
kind of implicit in allowing someone to push to your repo?
- Ted
next prev parent reply other threads:[~2011-09-10 23:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 20:01 [PATCH v2 0/7] "push -s" Junio C Hamano
2011-09-08 20:01 ` [PATCH v2 1/7] send-pack: typofix error message Junio C Hamano
2011-09-08 20:01 ` [PATCH v2 2/7] Split GPG interface into its own helper library Junio C Hamano
2011-09-08 20:01 ` [PATCH v2 3/7] push -s: skeleton Junio C Hamano
2011-09-08 20:01 ` [PATCH v2 4/7] push -s: send signed push certificate Junio C Hamano
2011-09-08 20:01 ` [PATCH v2 5/7] push -s: receiving end Junio C Hamano
2011-09-08 20:01 ` [PATCH v2 6/7] refactor run_receive_hook() Junio C Hamano
2011-09-08 20:01 ` [PATCH v2 7/7] push -s: support pre-receive-signature hook Junio C Hamano
2011-09-09 20:41 ` [PATCH v3 0/4] Signed push Junio C Hamano
2011-09-09 20:41 ` [PATCH v3 1/4] send-pack: typofix error message Junio C Hamano
2011-09-09 20:41 ` [PATCH v3 2/4] Split GPG interface into its own helper library Junio C Hamano
2011-09-09 20:41 ` [PATCH v3 3/4] rename "match_refs()" to "match_push_refs()" Junio C Hamano
2011-09-09 20:41 ` [PATCH v3 4/4] push -s: signed push Junio C Hamano
2011-09-09 21:16 ` [PATCH v3.1 " Junio C Hamano
2011-09-10 5:19 ` [PATCH v3 0/4] Signed push Junio C Hamano
2011-09-10 15:17 ` Sverre Rabbelier
2011-09-10 16:30 ` Junio C Hamano
2011-09-10 19:22 ` Ted Ts'o [this message]
2011-09-11 1:42 ` Junio C Hamano
2011-09-11 8:53 ` Sverre Rabbelier
2011-09-11 15:51 ` Ted Ts'o
2011-09-10 20:05 ` Robin H. Johnson
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110910192225.GA5397@thunk.org \
--to=tytso@mit.edu \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=spearce@spearce.org \
--cc=srabbelier@gmail.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.
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 NNTP newsgroup(s).