[Python-Dev] Committing a bug fix (original) (raw)
Brett Cannon brett at python.org
Mon Sep 28 19:23:44 CEST 2015
- Previous message (by thread): [Python-Dev] Committing a bug fix
- Next message (by thread): [Python-Dev] Committing a bug fix
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
See http://bugs.python.org/issue18967 if you want to join the discussion on how to solve Misc/NEWS potentially in the short term (long term we have a plan once someone has time to hack on the issue tracker).
On Mon, 28 Sep 2015 at 10:12 Alexander Belopolsky < alexander.belopolsky at gmail.com> wrote:
On Mon, Sep 28, 2015 at 4:13 AM, Terry Reedy <tjreedy at udel.edu> wrote:
Normal one specified in devguide: commit 3.4, merge 3.5, merge 3.6, That's exactly what I did at fist, but apparently while I was doing this, another commit was pushed to all three branches. To recover, I did a series of hg update 3.x; hg merge dances fighting with Misc/NEWS on every turn.
Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/brett%40python.org -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20150928/8ce33be1/attachment.html>
- Previous message (by thread): [Python-Dev] Committing a bug fix
- Next message (by thread): [Python-Dev] Committing a bug fix
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]