On Mar 7, 2011, at 4:15 PM, Colin Barrett wrote:
>
>
> On Mar 7, 2011, at 10:40 AM, Zachary West wrote:
>
>> On Mon, Mar 7, 2011 at 13:00, Colin Barrett <[email protected]>
>> wrote:
>>> On Mar 7, 2011, at 1:41 AM, Peter Hosey wrote:
>>>
>>>> On Mar 6, 2011, at 17:12:00, [email protected] wrote:
>>>>> details: http://hg.adium.im/adium-1.4/rev/f46d14768090
>>>>> revision: 3382:f46d14768090
>>>>> author: Colin Barrett <[email protected]>
>>>>> date: Sun Mar 06 17:09:40 2011 -0800
>>>>
>>>> If possible, it would be good if commit emails included the branch name.
>>>> Ideally, only when it isn't default, but unconditionally would be OK, too.
>>>
>>> Does anyone know how these emails are sent? I checked the hgrcs for the
>>> both adium and adium-1.4 (on eider) and I only saw the buildbot hook.
>>>
>>> -Colin
>>>
>>
>> Look up a level at the hg user's ~/.hgrc -- all the multi-repo stuff goes
>> there.
>
> Done.
>
> New emails on default should have "branch: (none)"; emails on branches will
> have "branch: branchname". It's not ideal, but {branches} returns an empty
> string for csets on default, and the only filter to deal w/ that is
> `nonempty`, which turns empty string into (none).
Use the {branch} keyword instead. Might be 1.8-only, but that'll DTRT for ya.
For the curious: {branches} is a now-deprecated (as of 1.8) artifact of an
older implementation of named branches that didn't pan out.
>
> -Colin
>
>
