Re: [platform-ui-dev] Commit message guidelines

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

Re: [platform-ui-dev] Commit message guidelines

From: Dean Roberts <Dean_Roberts@xxxxxxxxxx>
Date: Fri, 24 Feb 2012 10:08:23 -0500
Delivered-to: platform-ui-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/platform-ui-dev>
List-help: <mailto:platform-ui-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/platform-ui-dev>, <mailto:platform-ui-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/platform-ui-dev>, <mailto:platform-ui-dev-request@eclipse.org?subject=unsubscribe>

I also agree with John et. al.

Placing the bug number and title on the 1st line also means that is what we see in the Eclipse (EGit) History view. Which, I believe, is a good thing.

I'm fine with a short blurb describing the work. I'm even OK with re-iterating the bug number on the last line if it helps tooling. But I would wonder if we couldn't just alter the tooling to look for a bug number as the 1st thing in the comment.

Dean_Roberts@xxxxxxxxxx

References:
- [platform-ui-dev] Commit message guidelines
  - From: Paul Webster
- Re: [platform-ui-dev] Commit message guidelines
  - From: John Arthorne
- Re: [platform-ui-dev] Commit message guidelines
  - From: Paul Webster
- Re: [platform-ui-dev] Commit message guidelines
  - From: Markus Keller

Prev by Date: Re: [platform-ui-dev] Commit message guidelines
Next by Date: Re: [platform-ui-dev] Commit message guidelines
Previous by thread: Re: [platform-ui-dev] Commit message guidelines
Next by thread: Re: [platform-ui-dev] Commit message guidelines
Index(es):
- Date
- Thread

Breadcrumbs