Typically the standard we use is:
Fixed #123: issue 123 summary as in the bug tracker
Fixed #345: issue 345 summary as in the bug tracker
Note that whatever is after the # can be copied from the summary field in
the bugtracker view page.
Then following these header line(s), we enter any extra comments about the
fix or whatever else we want to include in the log.
On Fri, Aug 22, 2008 at 2:01 PM, Gianluca Sforna <[EMAIL PROTECTED]> wrote:
> On Fri, Aug 22, 2008 at 7:43 PM, KM <[EMAIL PROTECTED]> wrote:
> >
> > Is there any way to make the script know that xxx,yyy are two issues to
> be
> > noted. I thought maybe I missed something easy with my regular
> expression,
> > or anything else. I am not really into re-writing the php :-)
>
> Well, I could comment on your regexp if you posted it here ;)
>
> However, I think you could obtain what you need by useing something like:
>
> resolved issue: 998
> resolved issue: 999
>
> as commit message
>
> Cheers
>
> Gianluca
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> mantisbt-help mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mantisbt-help
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
mantisbt-help mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mantisbt-help
