On 27 February 2011 05:12, Barry Warsaw <barry at python.org> wrote: > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20110227/74e5946f/attachment.html>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4