[Tracker-discuss] [issue382] Bad CC on review

2018-06-12 Thread Berker Peksag
Berker Peksag added the comment: The recommended way of contributing to Python is now GitHub pull requests and we no longer maintain our Rietveld instance. Closing this issue. -- nosy: +berker.peksag status: chatting -> resolved __

[Tracker-discuss] [issue382] Bad CC on review

2011-07-19 Thread Antoine Pitrou
Antoine Pitrou added the comment: True. However, it regularly bites some people and is quite unpractical. ___ PSF Meta Tracker ___ ___

[Tracker-discuss] [issue382] Bad CC on review

2011-07-19 Thread Ezio Melotti
Ezio Melotti added the comment: Adding a message on the tracker and let roundup sending a mail to the nosy members will avoid this problem. See also #394. -- nosy: +ezio.melotti ___ PSF Meta Tracker

[Tracker-discuss] [issue382] Bad CC on review

2011-06-16 Thread Éric Araujo
Éric Araujo added the comment: I’ve sent a number of reviews to unexpanded names, thinking that Roundup would replace them with the email addresses :/ -- nosy: +eric.araujo status: unread -> chatting ___ PSF Meta Tracker

[Tracker-discuss] [issue382] Bad CC on review

2011-03-26 Thread Antoine Pitrou
New submission from Antoine Pitrou : In http://bugs.python.org/review/11393, the computed "CC" of review e-mails is bad: "m...@egenix.com, sc...@scottdial.com, Antoine Pitrou, haypo, arfrever@gmail.com, Trundle, dmalc...@redhat.com" You'll notice that some people (Antoine Pitrou, haypo, T