On 2016-11-10 22:46, Lawrence Velázquez wrote:
>> On Nov 10, 2016, at 9:57 AM, Ryan Schmidt <[email protected]> wrote:
>
>> It should recognize "Resolves"; we've been using that in Subversion
>> commit messages for years.
"closes" and "fixes" are much more popular than "resolves":
$ git log --oneline --grep=resolves -i |wc -l
201
$ git log --oneline --grep=fixes -i |wc -l
2483
$ git log --oneline --grep=closes -i |wc -l
3893
> The supported keywords are documented on the wiki [1]. They come from
> upstream [2] and wouldn't be hard to extend, if upstream was open to it.
>
> [1] https://trac.macports.org/wiki/CommitMessages#keywords
> [2]
> https://trac.edgewall.org/browser/branches/1.2-stable/tracopt/ticket/commit_updater.py#L118
Actually you just linked to the very configuration option that would
allow us to change it in conf/trac.ini in the trac.macports.org repository.
Is there really a need to do so? I would prefer a smaller set of
distinct commands over a lot of different keywords for the same thing.
By the way, we are using Trac 1.0 at the moment. Trac 1.2 was only
released a few days ago, see https://trac.macports.org/ticket/52835.
Rainer
