Re: Fw: Proposal: remove commit_timestamp.json

2016-10-17 Thread Edward K. Ream
On Mon, Oct 17, 2016 at 11:57 AM, Jacob Peck wrote: ​> ​ Why is this suddenly an issue? ​A better answer is that I have been working on distribution for the last three days. Problems come up in that context that we completely ignore normally. Let's be clear. The new

Re: Fw: Proposal: remove commit_timestamp.json

2016-10-17 Thread 'Terry Brown' via leo-editor
From: Edward K. Ream <edream...@gmail.com> To: leo-editor <leo-editor@googlegroups.com> Sent: Monday, October 17, 2016 1:40 PM Subject: Re: Fw: Proposal: remove commit_timestamp.json On Mon, Oct 17, 2016 at 11:57 AM, Jacob Peck <gatesph...@gmail.com> wrote:

Re: Fw: Proposal: remove commit_timestamp.json

2016-10-17 Thread Edward K. Ream
On Mon, Oct 17, 2016 at 11:57 AM, Jacob Peck wrote: > I'm with Terry on this -- the commit_timestamp.json file has been > immensely helpful in debugging user issues in the past. Relegating the > commit hash to some funky filename is not an acceptable option. > ​Ok. I can

Re: Fw: Proposal: remove commit_timestamp.json

2016-10-17 Thread Jacob Peck
I'm with Terry on this -- the commit_timestamp.json file has been immensely helpful in debugging user issues in the past. Relegating the commit hash to some funky filename is not an acceptable option. Git hooks are painless. Why is this suddenly an issue? -->Jake On 10/17/2016 12:50 PM,

Fw: Proposal: remove commit_timestamp.json

2016-10-17 Thread 'Terry Brown' via leo-editor
[meant to post to the list, not just Edward] From: Edward K. Ream To: leo-editor Cc: terry_n_br...@yahoo.com Sent: Monday, October 17, 2016 11:23 AM Subject: Re: Proposal: remove commit_timestamp.json On Monday, October 17, 2016 at