db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Matrigali <mikem_...@sbcglobal.net>
Subject Re: reminder - don't use DERBY-XXXX: text format in svn commits (colon defeats JIRA/svn integration)
Date Wed, 16 Feb 2011 20:59:03 GMT
Rick Hillegas wrote:
> On 2/16/11 11:56 AM, Knut Anders Hatlen wrote:
>> Mike Matrigali<mikem_app@sbcglobal.net>  writes:
>>
>>> Just a reminder to not put colon after your derby number in svn commits.
>>> This defeats the automatic mechanism that JIRA uses to make your svn
>>> commits show up in the JIRA history for an issue.  It really makes
>>> backporting fixes hard when you can't see the commits in the JIRA.
>>>
>>> For instance the following svn commit will not show up:
>>>
>>> DERBY-4711: Hung thread after another thread is interrupted
>>>
>>> If a thread fails while waiting for a lock, remove that thread from
>>> the queue.
>>>
>>>
>>> While the following will:
>>> DERBY-4711  Hung thread after another thread is interrupted
>>>
>>> If a thread fails while waiting for a lock, remove that thread from
>>> the queue.
>> That's odd... I've always been using a colon, and looking at
>> https://issues.apache.org/jira/browse/DERBY-5032 the following commit
>> message indeed does show up when I click on "Subversion Commits":
>>
>> ,----
>> | DERBY-5032: derived InternalXact attempts (and fails) to override a 
>> method from base
>> |
>> | Patch contributed by Dave Brosius<dbrosius@apache.org>.
>> `----
>>
> This is the first I have heard about this problem. Like Knut, I have 
> been putting colons in my commit messages for years. When did people 
> start noticing this problem? That may help us track it down.
> 
> Thanks,
> -Rick
> 
Looking at it closer it does seem like sometimes it works and sometimes
it does not.  I just assumed it was consistent.  It does not seem to be
consistent with a user also.  For instance DERBY-5015 by knut does not 
show a svn commit for me, while 5032 does.



Mime
View raw message