W3C home > Mailing lists > Public > public-aria-editors@w3.org > June 2016

Re: Commit history

From: Joanmarie Diggs <jdiggs@igalia.com>
Date: Mon, 6 Jun 2016 21:10:34 -0400
To: Matt King <mck@fb.com>
Cc: "public-aria-editors@w3.org" <public-aria-editors@w3.org>
Message-ID: <663588b8-146e-c0e5-3dd4-a0e1dd81d07c@igalia.com>
Hey Matt.

That's probably my fault. Some of your commit messages when working in
local branches were so thoroughly detailed that I assumed they were
meant for those reading your proposed changes and not something to be
included in the final version. Next time I will check with you before
making erroneous assumptions.

I'm really sorry.
--joanie

On 06/06/2016 08:45 PM, Matt King wrote:
> I was just looking back in commit logs for commit messages I wrote about
> changes for my actions.
> 
>  
> 
> I was being careful to write detailed messages  so that when the
> branches evaporated my summaries of changes, and where important, short
> bits about the reasons for the changes, would be readily available.
> 
>  
> 
> It seems that when I deleted branches, the commit messages have gone
> even though the commits have been merged to master.
> 
>  
> 
> In some cases, I kept a list of changes handy in an off-line file so I
> can reconstruct it. In cases where I was really on top of things, I
> wrote a summary in the action item. But, still, the easiest way to get a
> list of changes is to look at commit logs. That way you donít have to
> dig through lots of actions and issues and so forth.
> 
>  
> 
> I donít understand how this information has disappeared. AmI
> misunderstanding what we should be putting into commit messages and how
> commits are merged? I was really counting on using the messages to hold
> important info. And, I was also banking on GIT as a way for me to keep
> track of contributions.
> 
>  
> 
> MattKing
> 
Received on Tuesday, 7 June 2016 01:11:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 7 June 2016 01:11:11 UTC