Email subject line formatting
Magnus Ihse Bursie
magnus.ihse.bursie at oracle.com
Fri Apr 17 06:57:38 UTC 2020
On 2020-04-14 20:32, mark.reinhold at oracle.com wrote:
> 2020/4/14 1:18:20 -0700, magnus.ihse.bursie at oracle.com:
>> On 2020-04-14 09:58, Magnus Ihse Bursie wrote:
>>> Perhaps Jon is onto something that we should be more aggressive in how
>>> the subject line is rewritten. When a change is actually integrated,
>>> it is technically no longer a "RFR", so maybe rewrite to "Integrate:
>>> Bug description ..." instead? As long as the In-Reply-To mail header
>>> is correct, mail software should get the threading right regardless of
> That would be preferable.
>> I also realise that on projects where a commit can be pushed without a
>> review, the commit message is sent out as "FYI: Bug description...".
>> This has also confused me, since it sounded like someone wanted to
>> inform me about something, and not an auto-generated commit mail. Using
>> "Integrated: Bug description..." would be beneficial here as well, I think.
> Is that always the case? Or is there still the option (per-project,
> I’d assume) to get the traditional “git: jdk/jdk: 87654321: ...” style
> of message for commits that are not formally reviewed?
I don't know. I'm just passively following some of the projects that
have migrated, and I started noticing these "FYI" mails some time ago,
so I guess it's an option for the project to turn them on or not.
Someone in the Skara team is probably better suited to answer that question.
> - Mark
More information about the skara-dev