db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut Anders Hatlen <knut.hat...@oracle.com>
Subject Re: reminder - don't use DERBY-XXXX: text format in svn commits (colon defeats JIRA/svn integration)
Date Wed, 16 Feb 2011 19:56:49 GMT
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>. 
`----

-- 
Knut Anders

Mime
View raw message