[jdt-ui-dev] Always need for bug # in commit msg?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[jdt-ui-dev] Always need for bug # in commit msg?

From: Robin Henricsson <robinhenricsson@xxxxxxxxx>
Date: Fri, 21 Nov 2014 21:11:48 +0100
Delivered-to: jdt-ui-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/jdt-ui-dev>
List-help: <mailto:jdt-ui-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/jdt-ui-dev>, <mailto:jdt-ui-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/jdt-ui-dev>, <mailto:jdt-ui-dev-request@eclipse.org?subject=unsubscribe>

I've been using Eclipse for Java development for a couple of years now, and may have found a JDT issue on BugZilla that I would like to fix, thereby contributing to the great product I use on a daily basis.

The thing is, though, that I've never worked on an open source project before and so I would like to start off by committing something a bit smaller and easier. I have found some code that I believe does not quite follow the code convention and thought of updating it.

The contribution wiki page (http://wiki.eclipse.org/JDT_UI/How_to_Contribute) says that I need to include the bug number in the commit message. Do I need to file a bug report for the code convention deviations or can I just go ahead and fix them and then push to Gerrit?

Thanks a lot in advance, I look forward to getting into this.
Regards
Robin

Robin Henricsson
RobinHenricsson@xxxxxxxxx
0734292332

Follow-Ups:
- Re: [jdt-ui-dev] Always need for bug # in commit msg?
  - From: Daniel Megert

Prev by Date: [jdt-ui-dev] Test Plan for Mars M3 Test Pass
Next by Date: Re: [jdt-ui-dev] Always need for bug # in commit msg?
Previous by thread: [jdt-ui-dev] Test Plan for Mars M3 Test Pass
Next by thread: Re: [jdt-ui-dev] Always need for bug # in commit msg?
Index(es):
- Date
- Thread

Breadcrumbs