Re: [Python-Dev] [Python-checkins] cpython: improve license
Notice the subject line. Can we make commit messages contain the named branch that the change applies to? The 'cpython' in the header doesn't really tell me whether I should care about this diff or not. Say the change applied to 2.6 but I only care about Python 3. It would be nice if I could just delete this message without reading the body. I guess it's possible for change notifications to encompass multiple named branches though, right? I'm not sure what to do about that, but it seems like a less common use case. -Barry On Feb 26, 2011, at 07:05 PM, benjamin.peterson wrote:
benjamin.peterson pushed 0873fb83f1e2 to cpython:
http://hg.python.org/cpython/rev/0873fb83f1e2 changeset: 68052:0873fb83f1e2 tag: tip user: Benjamin Peterson
date: Sat Feb 26 12:06:36 2011 -0600 summary: improve license files: LICENSE
Am 26.02.2011 19:12, schrieb Barry Warsaw:
Notice the subject line. Can we make commit messages contain the named branch that the change applies to?
If you don't want this request to be forgotten, add it to todo.txt in the pymigr repo. Regards, Martin
On 27 February 2011 05:12, Barry Warsaw
I guess it's possible for change notifications to encompass multiple named branches though, right? I'm not sure what to do about that, but it seems like a less common use case.
Are the change notifications per-commit? If so, there's no way that a single change notification could be for more than one named branch. If the notifications are per-pull/per-push, then yes it could be for multiple branches. In either case, it should definitely be possible to put the name(s) of the branches in the change notifications - in either type of hook you can inspect the changesets and determine what branch they are on. Tim Delaney
participants (3)
-
"Martin v. Löwis"
-
Barry Warsaw
-
Tim Delaney