Anyone knows how to set up autonosy on roundup? I only get information about new tickets and then I don't get followups.
On 17 March 2010 14:36, Michael Hudson-Doyle <micahel@gmail.com> wrote:
On 17 March 2010 14:30, Maciej Fijalkowski <fijall@gmail.com> wrote:
Anyone knows how to set up autonosy on roundup? I only get information about new tickets and then I don't get followups.
I think it involves editing a particular file on codespeak. Yay!
In particular, /www/codespeak.net/issue/pypy-dev/detectors/nosyreaction.py Cheers, mwh
2010/3/17 Antonio Cuni <anto.cuni@gmail.com>
Benjamin Peterson wrote:
2010/3/16 Maciej Fijalkowski <fijall@gmail.com>:
Anyone knows how to set up autonosy on roundup? I only get information about new tickets and then I don't get followups.
When that's figured out, I'd also like to be on autonosy.
me too :-)
What about a mailing list, similar to Python-bugs-list? -- Amaury Forgeot d'Arc
Hi, On Wed, Mar 17, 2010 at 10:19:19AM +0100, Amaury Forgeot d'Arc wrote:
What about a mailing list, similar to Python-bugs-list?
That's a very good idea, but unfortunately I don't know if there are issues, like what occurs when you reply to an e-mail in that list. It probably just works if the mailing list is configured so that replies go by default to the author of the mail instead of to the list's address. If that's not an issue then I could make the mailing list (provided maybe with some reminder of how I'm supposed to do that on codespeak...). A bientot, Armin.
Hi, On Tue, Mar 23, 2010 at 12:49 +0100, Armin Rigo wrote:
Hi,
On Wed, Mar 17, 2010 at 10:19:19AM +0100, Amaury Forgeot d'Arc wrote:
What about a mailing list, similar to Python-bugs-list?
That's a very good idea, but unfortunately I don't know if there are issues, like what occurs when you reply to an e-mail in that list. It probably just works if the mailing list is configured so that replies go by default to the author of the mail instead of to the list's address. If that's not an issue then I could make the mailing list (provided maybe with some reminder of how I'm supposed to do that on codespeak...).
head to http://codespeak.net/mailman/create and look into /root/.ssh/mmsitepass for password (requires root) H.
Hi, On Tue, Mar 23, 2010 at 05:28:38PM +0100, holger krekel wrote:
What about a mailing list, similar to Python-bugs-list?
Done. The list is there: http://codespeak.net/mailman/listinfo/pypy-issue Note that I did not remove the existing hacks. Please ask me. One issue is that I'm not sure how to make "pypy-issue" autonosy on the already-existing tracker entries -- so far I fear that it's going to receive only the new entries (including follow-ups to that). A bientot, Armin.
Re-hi, On Tue, Mar 23, 2010 at 06:38:32PM +0100, Armin Rigo wrote:
Note that I did not remove the existing hacks. Please ask me. One issue is that I'm not sure how to make "pypy-issue" autonosy on the already-existing tracker entries -- so far I fear that it's going to receive only the new entries (including follow-ups to that).
That's done too now. A number of people should be removed from the "nosy" field as soon as there is a new posting to a existing or new issue. Additionally, "pypy-issue" should show up in the "nosy" field. It goes to the new mailing list, to which I already subscribed precisely the same list of people. (This means that you're still getting all mails from the tracker, but now coming from pypy-issue@codespeak.net, so your mail filters may need some re-tweaking.) For everybody else, please feel free to subscribe at http://codespeak.net/mailman/listinfo/pypy-issue . A bientot, Arin.
participants (7)
-
Amaury Forgeot d'Arc -
Antonio Cuni -
Armin Rigo -
Benjamin Peterson -
holger krekel -
Maciej Fijalkowski -
Michael Hudson-Doyle