From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Sitaram Chamarty <sitaramc@gmail.com>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
"Randal L. Schwartz" <merlyn@stonehenge.com>,
git@vger.kernel.org
Subject: Re: thoughts on a possible "pre-upload" hook
Date: Fri, 25 Sep 2009 14:29:47 +0200 [thread overview]
Message-ID: <vpqab0j1a2s.fsf@bauges.imag.fr> (raw)
In-Reply-To: <2e24e5b90909250454s7ed35b9ch10b954b0b1a40cfe@mail.gmail.com> (Sitaram Chamarty's message of "Fri\, 25 Sep 2009 17\:24\:36 +0530")
Sitaram Chamarty <sitaramc@gmail.com> writes:
> yes indeed -- if someone were to foolishly merge a "secret" branch
> into a "normal" branch, so that it is now reachable from a "normal"
> branch, that's his problem -- that cannot be within the scope of this
> check.
Merging is not the only scenario. Adding a tag could make secret
things become visible too. I'm not saying the approach isn't viable,
but if it gets implemented, it should be done with care to make sure
there's no easy mis-use that would lead to reveal a secret (typically,
I'd do that with a whitelist and not a black-list, so that new
references are secret by default).
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2009-09-25 12:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 10:20 thoughts on a possible "pre-upload" hook Sitaram Chamarty
2009-09-22 16:00 ` Randal L. Schwartz
2009-09-22 16:05 ` Matthieu Moy
2009-09-22 16:17 ` Shawn O. Pearce
2009-09-25 11:54 ` Sitaram Chamarty
2009-09-25 12:29 ` Matthieu Moy [this message]
2009-09-25 13:43 ` Sitaram Chamarty
2009-09-28 2:01 ` Adam Brewster
2009-09-28 3:02 ` Sitaram Chamarty
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=vpqab0j1a2s.fsf@bauges.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.com \
--cc=sitaramc@gmail.com \
--cc=spearce@spearce.org \
/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).