[TYPO3-core] Convention for topic in Gerrit

Alexander Stehlik alexander.stehlik at gmail.com
Fri Oct 18 09:52:21 CEST 2013

Hi Markus,

thanks for clearing that up.


Am 17.10.2013 23:38, schrieb Markus Klein:
> Hi!
> In former times, when Gerrit didn't support to use the Change-Id in multiple branches, we used the forge ticket number as topic to "group" patches and corresponding backports.
> Today we Gerrit allows to use the Change-Id for this, hence you can choose whatever you like as topic. No topic at all is ok as well.
> It does make sense to specify a topic for multiple related patches for bigger changes though.
> Kind regards
> Markus
> ------------------------------------------------------------
> Markus Klein
> TYPO3 CMS Active Contributors Team Member
>> -----Original Message-----
>> From: typo3-team-core-bounces at lists.typo3.org [mailto:typo3-team-core-
>> bounces at lists.typo3.org] On Behalf Of Alexander Stehlik
>> Sent: Thursday, October 17, 2013 11:25 PM
>> To: typo3-team-core at lists.typo3.org
>> Subject: [TYPO3-core] Convention for topic in Gerrit
>> Hi folks,
>> a short question about Gerrit: is there a convention about the topic that
>> should be used for a commit. Sometimes an issue ID is uses, sometimes
>> nothing at all and sometimes a speaking topic is set.
>> Are there any conventions / best practices for that?
>> Cheers,
>> Alex
>> _______________________________________________
>> Before posting to this list, please have a look to the posting rules on the
>> following websites:
>> http://typo3.org/teams/core/core-mailinglist-rules/
>> http://typo3.org/development/bug-fixing/diff-and-patch/
>> _______________________________________________
>> TYPO3-team-core mailing list
>> TYPO3-team-core at lists.typo3.org
>> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-team-core

More information about the TYPO3-team-core mailing list