Hi,
On Tue, Feb 18, 2014 at 9:23 AM, Jason Stephenson wrote:
> Is this something you want applied retroactively to branches that are
> waiting to go into master now, or is this request more for future
> branches that get created?
Better now than never. I won't stamp my feet if it doesn't get
ap
Is this something you want applied retroactively to branches that are
waiting to go into master now, or is this request more for future
branches that get created?
I can see this causing some headaches if it is to be applied to existing
branches with more than a handful of commits.
--
Jason Steph
+1
This would be very helpful tracking the rationale behind certain changes we
encounter.
- Original Message -
> From: "Bill Erickson"
> To: "Evergreen Development Discussion List"
>
> Sent: Monday, February 17, 2014 1:50:09 PM
> Subject: Re:
+1.
-b
On Mon, Feb 17, 2014 at 1:06 PM, Galen Charlton wrote:
> Hi,
>
> I'd like to request that we all get in the habit of including bug
> numbers in commit messages -- specifically, in the first line. Doing
> this will make it easier to work backwards from a commit to the
> description of t
Hi,
I'd like to request that we all get in the habit of including bug
numbers in commit messages -- specifically, in the first line. Doing
this will make it easier to work backwards from a commit to the
description of the bug it fixes without having to fight LP's search
engine. It will also make
