From: Johannes Berg <johannes@sipsolutions.net>
To: backports@vger.kernel.org
Subject: Re: backports test automation
Date: Tue, 25 Sep 2018 21:24:02 +0200 [thread overview]
Message-ID: <1537903442.3387.19.camel@sipsolutions.net> (raw)
In-Reply-To: <1537881030.3387.12.camel@sipsolutions.net> (sfid-20180925_151043_638811_F7DF4797)
On Tue, 2018-09-25 at 15:10 +0200, Johannes Berg wrote:
>
> Another thing I should say is that I'm trying to avoid having automation
> that manipulates the git tree (even adding tags) since we have no
> permission model for that and kernel.org trees are supposed to be
> controlled by people, afaict.
Konstantin informed me that he *does* have a way to do per-ref
permissions, so it sounds like in theory we could add a notes ref for
some automation to write test things etc. to. I don't think gitolite
supports a permission check for "just a tag", so I think that's still
out.
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
prev parent reply other threads:[~2018-09-26 1:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 13:10 backports test automation Johannes Berg
2018-09-25 19:24 ` Johannes Berg [this message]
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=1537903442.3387.19.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=backports@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).