[Nick]
>[me]
>> IIRC, you can’t know who pushed without kludgy hackery.
>
> [...] Note that the current distutils2 emails to python-checkins
> already say "Tarek Ziade pushed..."
I looked at mail.py in the hooks repository and learned that hooks get
an HGPUSHER variable in their environment. Nice
On 14 July 2010 18:26, Dirkjan Ochtman wrote:
> On Wed, Jul 14, 2010 at 10:15, Georg Brandl wrote:
> > I also don't think we will see pushes like Tarek's 100+ one very often
> for
> > Python. Usually changes will be bug fixes, and unless the committer is
> > offline I expect them to be pushed i
On Wed, Jul 14, 2010 at 10:15, Georg Brandl wrote:
> I also don't think we will see pushes like Tarek's 100+ one very often for
> Python. Usually changes will be bug fixes, and unless the committer is
> offline I expect them to be pushed immediately.
Depends. If we do feature branches in separat
Am 14.07.2010 00:00, schrieb Nick Coghlan:
> On Wed, Jul 14, 2010 at 7:45 AM, Dirkjan Ochtman wrote:
>> On Tue, Jul 13, 2010 at 23:22, Nick Coghlan wrote:
>>> No, I meant push. There's a separate discussion where it was pointed
>>> out that publishing each commit as a separate email makes
>>> pyt
On Wed, Jul 14, 2010 at 7:45 AM, Dirkjan Ochtman wrote:
> On Tue, Jul 13, 2010 at 23:22, Nick Coghlan wrote:
>> No, I meant push. There's a separate discussion where it was pointed
>> out that publishing each commit as a separate email makes
>> python-checkins even chattier than it is already (th
On Tue, Jul 13, 2010 at 23:22, Nick Coghlan wrote:
> No, I meant push. There's a separate discussion where it was pointed
> out that publishing each commit as a separate email makes
> python-checkins even chattier than it is already (this point came up
> after Tarek pushed a distutils2 changeset c
On Wed, Jul 14, 2010 at 5:56 AM, Éric Araujo wrote:
>> I was actually going to suggest something along those lines post
>> transition, since Hg will have an email address for everyone - leave
>> push notifications coming from the bot (so existing filters based on
>> the bot address keep working),
