From: "Brian J. Johnson" <brian.johnson@hpe.com>
To: Laszlo Ersek <lersek@redhat.com>,
Jeremiah Cox <jerecox@microsoft.com>,
stephano <stephano.cetola@linux.intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [edk2-announce] Research Request
Date: Tue, 27 Nov 2018 15:55:52 -0600 [thread overview]
Message-ID: <fd97d913-2cf8-314d-2a3b-8473bc6ecfc5@hpe.com> (raw)
In-Reply-To: <76cb4d25-7eff-b19b-0dd5-2fcc3a1e7d82@redhat.com>
On 11/27/18 6:53 AM, Laszlo Ersek wrote:
> On 11/26/18 22:43, Jeremiah Cox via edk2-devel wrote:
>> Feedback on GitHub as follows…
>>
>>
>>> 1. No Lock-In - What automated data export is available?
>>> We want to be able to leave and take all our data with us. "Data" here
>>> includes: review comments, pull requests / patches (including metadata),
>>> old (rejected) pull requests and metadata, issue tracker entries and
>>> comments (if issue tracker included). This archiving should be
>>> automated, not something we do by hand.
>> Untested, but might these all be easily satisfied by subscribing a mailing list to GitHub notifications?
>> https://help.github.com/articles/about-notifications/#watching-notifications
>> https://help.github.com/articles/about-email-notifications/
> No, they are insufficient.
>
> Following the last link above ("about-email-notifications"), one finds
> several other links; and one of those is:
>
> https://help.github.com/articles/about-notifications/
>
> This article says,
>
> GitHub sends participating notifications when you're directly
> involved in activities or conversations within a repository or a
> team you're a member of. You'll receive a notification when:
>
> [...]
>
> - You open, comment on, or close an issue or pull request.
>
> [...]
>
> This is demonstrably false. I'm a member of the TianoCore organization,
> I have commented on, and closed (rejected):
>
> https://github.com/tianocore/edk2/pull/133
>
> and I *never* received an email notification about my *own* comment /
> action. I only received the initial email, about the pull request being
> opened (attached for reference).
Try going to the "Settings" item under the menu in the top-right corner,
and clicking on the "Notifications" tab on the left. Under "Email
notification preferences" there should be a checkbox for "Include your
own updates". That may do what you need.
--
Brian J. Johnson
Enterprise X86 Lab
Hewlett Packard Enterprise
next prev parent reply other threads:[~2018-11-27 21:55 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 18:34 [edk2-announce] Research Request stephano
2018-11-20 23:47 ` Jeremiah Cox
2018-11-21 0:58 ` stephano
2018-11-26 21:43 ` Jeremiah Cox
2018-11-26 22:27 ` stephano
2018-11-27 9:33 ` Knop, Ryszard
2018-11-27 21:16 ` Jeremiah Cox
2018-11-27 22:23 ` Rebecca Cran
2018-11-28 18:19 ` Jeremiah Cox
2018-11-28 19:21 ` Rebecca Cran
2018-11-27 12:53 ` Laszlo Ersek
2018-11-27 21:55 ` Brian J. Johnson [this message]
2018-11-28 11:07 ` Laszlo Ersek
2018-11-28 18:31 ` Jeremiah Cox
2018-11-28 22:01 ` Laszlo Ersek
2018-11-29 1:07 ` Jeremiah Cox
2018-11-29 9:48 ` Laszlo Ersek
2018-11-29 21:20 ` Rebecca Cran
2018-12-03 9:29 ` Laszlo Ersek
2018-12-03 21:39 ` Rebecca Cran
2018-12-04 18:00 ` Laszlo Ersek
2018-12-05 12:55 ` Laszlo Ersek
2018-12-05 17:26 ` Rebecca Cran
2018-12-06 14:05 ` Laszlo Ersek
2018-12-06 14:07 ` Laszlo Ersek
2018-12-06 14:13 ` Laszlo Ersek
2018-12-06 15:25 ` Rebecca Cran
2018-12-07 6:10 ` Rebecca Cran
2018-12-07 12:00 ` my Phabricator findings [was: Research Request] Laszlo Ersek
2018-12-07 13:11 ` Rebecca Cran
2018-12-05 17:31 ` [edk2-announce] Research Request Rebecca Cran
2018-12-06 13:51 ` Laszlo Ersek
2018-12-03 17:22 ` Jeremiah Cox
2018-12-04 18:26 ` Laszlo Ersek
2018-12-05 19:09 ` Jeremiah Cox
2018-12-06 13:33 ` Laszlo Ersek
2018-11-28 5:54 ` Desimone, Nathaniel L
2018-11-28 6:22 ` Stephano Cetola
2018-12-04 18:20 ` Philippe Mathieu-Daudé
2018-12-05 16:03 ` stephano
2018-12-12 13:20 ` GitLab results from my POV [was: Research Request] Laszlo Ersek
2018-12-20 17:46 ` Rebecca Cran
2019-01-10 20:17 ` about 'sr.ht' " Laszlo Ersek
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-list 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=fd97d913-2cf8-314d-2a3b-8473bc6ecfc5@hpe.com \
--to=devel@edk2.groups.io \
/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