public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Alexey Neyman <stilor@att.net>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
	"crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: Re: Publishing crosstool-ng pull requests on this list
Date: Tue, 13 Jun 2017 16:58:00 -0000	[thread overview]
Message-ID: <f9cbbd4f-b7da-8381-7e9d-af4f998b2990@att.net> (raw)
In-Reply-To: <ef27254bde474d2f812c1ca5b277f416@svr-chch-ex1.atlnz.lc>

Hi Chris,


On 06/08/2017 03:05 PM, Chris Packham wrote:
> Hi,
>
> At one point in the past Bryan commented that he'd like to see more
> active engagement in the review process from ct-ng contributors.
>
> Whenever something is pushed to the crosstool-ng repo we see a
> notification on the crossgcc list. Is there any way of doing the same
> for pull requests? That might provide more of a prompt for those that
> don't regularly look for new PRs on github.
I didn't find a knob for that in Github's settings for the repository: 
the email notifications are apparently only sent upon commits. There is 
an API for "webhooks" that can be notified on all activity - but that 
requires some proxy that will interpret that POST request and send out 
the email.

On the other hand, interested parties can "watch" the repository on 
Github and get notified about all activity, so I suggest you do that if 
you want to follow the development.

Regards,
Alexey.

      reply	other threads:[~2017-06-09  4:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-08 22:48 Chris Packham
2017-06-13 16:58 ` Alexey Neyman [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=f9cbbd4f-b7da-8381-7e9d-af4f998b2990@att.net \
    --to=stilor@att.net \
    --cc=Chris.Packham@alliedtelesis.co.nz \
    --cc=crossgcc@sourceware.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).