From: Junio C Hamano <gitster@pobox.com>
To: Roberto Tyley <roberto.tyley@gmail.com>
Cc: Stefan Beller <sbeller@google.com>,
Robert Dailey <rcdailey.lists@gmail.com>,
Heiko Voigt <hvoigt@hvoigt.net>,
Johannes Schindelin <johannes.schindelin@gmx.de>,
Jens Lehmann <Jens.Lehmann@web.de>, Git <git@vger.kernel.org>,
Thomas Ferris Nicolaisen <tfnico@gmail.com>,
emma@gitforteams.com
Subject: Re: [Announce] submitGit for patch submission (was "Diffing submodule does not yield complete logs")
Date: Fri, 22 May 2015 09:27:57 -0700 [thread overview]
Message-ID: <xmqq4mn4fugi.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAFY1edY3+Wt-p2iQ5k64Fg-nMk2PmRSvhVkQSVNw94R18uPV2Q@mail.gmail.com> (Roberto Tyley's message of "Fri, 22 May 2015 09:33:20 +0100")
Roberto Tyley <roberto.tyley@gmail.com> writes:
> Here's what a user does:
>
> * create a PR on https://github.com/git/git
> * logs into https://submitgit.herokuapp.com/ with GitHub auth
Hmm, this seems to request too much authorization, though.
Repositories
Public only
This application will be able to read and write all public repo
data. This includes the following:
Code
Issues
Pull requests
Wikis
Settings
Webhooks and services
Deploy keys
I really wanted to try this out, but I do not think, as the owner of
a reasonably important repository, it would be irresponsible for me
to grant write access to Code or Settings for my primary GitHub
account. Also I think you reject an account that is too young (I
found out about submitGit via your comment on a pull request to
git/git and read its source before reading your message I am
responding to, and that was the impression I got from the recent log
messages there), so I cannot create and try with a throw-away
account, either.
That would mean that I cannot join the fun X-<.
next prev parent reply other threads:[~2015-05-22 16:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 8:33 [Announce] submitGit for patch submission (was "Diffing submodule does not yield complete logs") Roberto Tyley
2015-05-22 9:42 ` Johannes Schindelin
2015-05-22 14:41 ` Johannes Schindelin
2015-05-22 17:14 ` Philip Oakley
2015-05-22 19:58 ` Johannes Schindelin
2015-05-22 21:35 ` Philip Oakley
2015-05-23 9:06 ` Johannes Schindelin
2015-05-22 13:06 ` Sebastian Schuberth
2015-05-22 13:25 ` Stefan Näwe
2015-05-22 14:17 ` Junio C Hamano
2015-05-22 17:40 ` Philip Oakley
2015-05-22 19:23 ` Stefan Beller
2015-05-22 19:59 ` Johannes Schindelin
2015-05-22 20:04 ` Junio C Hamano
2015-05-22 20:44 ` Stefan Beller
2015-05-23 9:11 ` Johannes Schindelin
2015-05-23 14:29 ` Matthieu Moy
[not found] ` <CAFY1edZ+5fW0FxQPO=qN6gqv8UfQUvjsutKvBOBj0CGbS8ms6A@mail.gmail.com>
2015-05-23 9:09 ` Johannes Schindelin
2015-05-22 16:14 ` Matthieu Moy
2015-05-22 16:27 ` Junio C Hamano [this message]
2015-05-22 16:53 ` Stefan Beller
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=xmqq4mn4fugi.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=Jens.Lehmann@web.de \
--cc=emma@gitforteams.com \
--cc=git@vger.kernel.org \
--cc=hvoigt@hvoigt.net \
--cc=johannes.schindelin@gmx.de \
--cc=rcdailey.lists@gmail.com \
--cc=roberto.tyley@gmail.com \
--cc=sbeller@google.com \
--cc=tfnico@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.
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).