Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (nike.apache.org: domain of charlesmchen@gmail.com
 designates 209.85.219.213 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=mMPMn5zDpDRoMVdvplGy3T3egjdvhCFrGgRJD4DYkgTZZfMX4Prkerv5HVZ1fL2cnZ
         z0aS3zvGDsGkErN2It+oLXrtkBlTkrB4/ojmcvJXyjLcg1SHHaQr3haQjO8IqyIM5tZw
         l2b5lKEtJd6ew2q+acKfbI/Qxg/TChANB60O0=
MIME-Version: 1.0
In-Reply-To: <31cc37360909121224i2b0922cct760b66054706e506@mail.gmail.com>
References: <ce1f2ea80909121138g2bf7e9baxfa4ffc5cb5d44c57@mail.gmail.com>
	 <31cc37360909121224i2b0922cct760b66054706e506@mail.gmail.com>
Date: Sat, 12 Sep 2009 16:02:15 -0400
Message-ID: <d020e6680909121302u7f69ddb2ke64daaaa3b0cae94@mail.gmail.com>
Subject: Re: [sanselan] Commit messages and JIRA ids [was: Resolved:
	(SANSELAN-26) Move ...]
From: Charles Matthew Chen <charlesmchen@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

   Thanks for the advice - I'll be sure to follow it.

Matthew


On Sat, Sep 12, 2009 at 3:24 PM, Henri Yandell <flamefew@gmail.com> wrote:
> The former is also crucial for anyone trying to work things out from
> your svn logs. Usually the commit message is quite low on information
> and having a link to the bugzilla entry or JIRA entry is great.
>
> The latter is less crucial but useful because a) svn commit tab in
> JIRA has been known to break and b) it makes it nice and easy to write
> the closing message in JIRA :) I just copy and paste my SVN
> input/output straight into the JIRA and both message, files involved
> and revision are now recorded.
>
> Hen
>
> On Sat, Sep 12, 2009 at 11:38 AM, Rahul Akolkar<rahul.akolkar@gmail.com> =
wrote:
>> Moved from issues@ ...
>>
>> Two requests:
>> =A0* Please add the issue identifier (such as SANSELAN-26 here) in the
>> SVN commit message(s) so commits appear in the "Subversion commits"
>> tab in the corresponding JIRA issue
>> =A0* For added measure, best to indicate the SVN revision for the fix in
>> the JIRA comment when resolving issue.
>>
>> TIA.
>> -Rahul
>>
>>
>> On Sat, Sep 12, 2009 at 1:42 PM, Charles Matthew Chen (JIRA)
>> <jira@apache.org> wrote:
>>>
>>> =A0 =A0 [ https://issues.apache.org/jira/browse/SANSELAN-26?page=3Dcom.=
atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>>
>>> Charles Matthew Chen resolved SANSELAN-26.
>>> ------------------------------------------
>>>
>>> =A0 =A0Resolution: Fixed
>>>
>>> =A0* Fixed a couple of platform-dependent paths in the tests.
>>> =A0* Constant-ized the magic numbers used when guessing formats.
>>> =A0* Added a test for the format guessing.
>>>
>>>
>>>> Move Image magic numbers to constants
>>>> -------------------------------------
>>>>
>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Key: SANSELAN-26
>>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 URL: https://issues.apache.org/jira/br=
owse/SANSELAN-26
>>>> =A0 =A0 =A0 =A0 =A0 =A0 Project: Commons Sanselan
>>>> =A0 =A0 =A0 =A0 =A0Issue Type: Improvement
>>>> =A0 =A0Affects Versions: 0.94-incubator
>>>> =A0 =A0 =A0 =A0 Environment: All
>>>> =A0 =A0 =A0 =A0 =A0 =A0Reporter: Ashish Paliwal
>>>> =A0 =A0 =A0 =A0 =A0 =A0Priority: Minor
>>>> =A0 Original Estimate: 1h
>>>> =A0Remaining Estimate: 1h
>>>>
>>>> All the Image magic numbers used in Sanselan.guessFormat() API can be =
moved to constants. As of now they are hardcoded within the API
>>>
>>> --
>>> This message is automatically generated by JIRA.
>>> -
>>> You can reply to this email to add a comment to the issue online.
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org