On 13/09/2017 08:17, Clemens Heuberger wrote:
Am 2017-09-12 um 20:48 schrieb Vincent Delecroix:
On 12/09/2017 20:46, Clemens Heuberger wrote:
Am 2017-09-12 um 20:33 schrieb Vincent Delecroix:
On 12/09/2017 20:32, Dima Pasechnik wrote:
ah, right, do not use git://, use
the same thing, g...@trac.sagemath.org:sage.git, for both push and fetch.
We should not force a user to upload her ssh key on trac in order to pull a
branch.
for patchbots, we cannot.
Why? We could force the patchbot user to have a trac account with an uploaded
ssh key and make the patchbot fetch via ssh. (of course we do not want to)
that would probably have to be a ssh key without passphrase. I'd feel more
comfortable if such a key would only have read-only access on trac's git.
No. You can use a the ssh keyring for that purpose.
So it would not longer be easy to "just run a patchbot".
Indeed. And anyway, you don't want the patchbot to have write access to
some branches on the git server.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.