[python-committers] Fwd: CPython repository - changeset not merged into default from 3.4?
I responded to Vinay, but I haven't heard back. I'm forwarding here in case someone else is impacted. I meant to make this change on the default branch only, but I accidentally made it on 3.4. If someone could revert it for me, I'd appreciate it. I'm away from a computer all day. I'll fix it when I get back. -- Eric. Begin forwarded message: > From: Vinay Sajip > Date: April 15, 2014 at 6:29:11 AM EDT > To: Eric Smith > Subject: CPython repository - changeset not merged into default from 3.4? > Reply-To: Vinay Sajip > > Hi Eric, > > I made some changes in the Python 3.4 branch which I want to merge into > default. I noticed that you made some changes in 3.4 in changeset > 16efa8d27e4c which don't appear in default - is this intentional? Your > changes are lumped in with mine when I try to merge :-( > > Regards, > > Vinay Sajip > ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Fwd: CPython repository - changeset not merged into default from 3.4?
Looks like this has been done http://hg.python.org/cpython/rev/4c65f8641d89 http://hg.python.org/cpython/rev/2d33cbf02522 The graph looks OK to me. http://hg.python.org/cpython/graph On Tue, Apr 15, 2014 at 7:36 AM, Eric V. Smith wrote: > I responded to Vinay, but I haven't heard back. I'm forwarding here in > case someone else is impacted. > > I meant to make this change on the default branch only, but I accidentally > made it on 3.4. If someone could revert it for me, I'd appreciate it. I'm > away from a computer all day. I'll fix it when I get back. > > -- > Eric. > > Begin forwarded message: > > *From:* Vinay Sajip > *Date:* April 15, 2014 at 6:29:11 AM EDT > *To:* Eric Smith > *Subject:* *CPython repository - changeset not merged into default from > 3.4?* > *Reply-To:* Vinay Sajip > > Hi Eric, > > I made some changes in the Python 3.4 branch which I want to merge into > default. I noticed that you made some changes in 3.4 in changeset > 16efa8d27e4c which don't appear in default - is this intentional? Your > changes are lumped in with mine when I try to merge :-( > > Regards, > > Vinay Sajip > > > ___ > python-committers mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-committers > > ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers
[python-committers] Small change to tracker 'resolution'
In a discussion at the sprints today Nick observed that 'invalid' was a
resolution that carried a rather negative subtext ("your bug report was
invalid", ie: "you made a mistake") , and that Red Hat used 'not a bug',
which we all agreed was much more descriptive of the actual resolution.
So, I've changed the text associated with the 'invalid' resolution
to read 'not a bug' instead.
--David
___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Small change to tracker 'resolution'
On 04/15/2014 05:55 PM, R. David Murray wrote: [...] I've changed the text associated with the 'invalid' resolution to read 'not a bug' [...] Nice. Any chance of changing the 'committed/rejected' text to something else? :) -- ~Ethan~ ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Small change to tracker 'resolution'
On Tue, Apr 15, 2014 at 9:45 PM, Ethan Furman wrote: > Any chance of changing the 'committed/rejected' text to something else? :) > Good that you brought this up. It always feels confusing to me. My suggestion is: Let's have committed for stuff that is committed Not committed for stuff that is not a bug. :-) ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Small change to tracker 'resolution'
On 15 Apr 2014 22:37, "Senthil Kumaran" wrote: > > > On Tue, Apr 15, 2014 at 9:45 PM, Ethan Furman wrote: >> >> Any chance of changing the 'committed/rejected' text to something else? :) > > > Good that you brought this up. It always feels confusing to me. > > My suggestion is: Let's have committed for stuff that is committed > > Not committed for stuff that is not a bug. Brett & David are working on a more general review of the tracker experience. This was just a quick & easy change to get things started :) Cheers, Nick. > > :-) > > > ___ > python-committers mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-committers > ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Small change to tracker 'resolution'
On 4/15/2014 8:55 PM, R. David Murray wrote:
In a discussion at the sprints today Nick observed that 'invalid' was a
resolution that carried a rather negative subtext ("your bug report was
invalid", ie: "you made a mistake") , and that Red Hat used 'not a bug',
which we all agreed was much more descriptive of the actual resolution.
So, I've changed the text associated with the 'invalid' resolution
to read 'not a bug' instead.
Thank you. I have usually looked for something else to use ;-).
___
python-committers mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-committers
Re: [python-committers] Small change to tracker 'resolution'
On 4/15/2014 9:45 PM, Ethan Furman wrote: On 04/15/2014 05:55 PM, R. David Murray wrote: [...] I've changed the text associated with the 'invalid' resolution to read 'not a bug' [...] Nice. Any chance of changing the 'committed/rejected' text to something else? :) Like 'finished'? 'completd'? 'done'? or even 'closed'? ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers
