Just going to add another +1 from my support experience.
In the past I have quite often found that I am either investigating a
bug that has already been fixed in a later release or occasionally
investigating a bug which has been introduced as a result of a another
fix - having clear commit messages with the Jira ID and some simple text
describing the fix makes it a lot easier to work with the history.
Regards,
Darran Lofthouse.
On 04/18/2011 08:33 AM, Heiko Braun wrote:
+1
On Apr 16, 2011, at 3:00 PM, Jason Greene wrote:
> I think this is a good practice.
>
> Sent from my iPhone
>
> On Apr 16, 2011, at 3:40 AM, "Heiko W.Rupp"<hrupp(a)redhat.com>
wrote:
>
>> Hi,
>>
>> while a jira number points to the issue / new feature, only having this in the
commit message
>> is not nice when browsing for changes.
>>
>>> From the github rss feed:
>>
>> • maeste committed 5dcb774
>> JBAS-9334
>>
>> As the jira-id is not clickable it is cumbersome to lookup, to see if this is
something
>> "of interest".
>>
>> So my plea: please also add a short description or the jira subject line to the
commit message
>>
>> Heiko
>>
>> --
>> Reg. Adresse: Red Hat GmbH, Technopark II, Haus C,
>> Werner-von-Siemens-Ring 14, D-85630 Grasbrunn
>> Handelsregister: Amtsgericht München HRB 153243
>> Geschaeftsführer: Brendan Lane, Charlie Peters, Michael Cunningham, Charles
Cachera
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev