Re: Recording the current branch on each commit?

From: Sitaram Chamarty <sitaramc@gmail.com>
Date: Apr 28, 2014, 10:03 UTC
Message-ID: <535E277C.9070502@gmail.com>
In-Reply-To: <535E16D4.9040509@game-point.net>

On 04/28/2014 02:22 PM, Jeremy Morton wrote:

Show 14 quoted lines

> On 28/04/2014 03:30, Sitaram Chamarty wrote:
>> On 04/28/2014 01:03 AM, Johan Herland wrote:
>>> Yeah, sure. Author and Date (and Committer, for that matter) is just
>>> metadata, and the current branch name is simply just another kind of
>>> metadata. All of them are more-or-less free-form text fields, and off
>>
>> no they're not. In strictly controlled environments they form part of
>> the audit record for the source code.
>>
>> Yes they can be faked (explicitly), but -- again in strictly controlled
>> environments -- that can be limited to "before it was first pushed".
>
> Why these specific headers as part of the audit record, though?
> Aren't you just arbitrarily defining them as part of the audit record?

"who did it" and "when did they do it" are a fair bit more central to "how did we get here" (viz., the SHA1 of the top commit, if you will) than "what branch was this commit born in (or similar)".

Here's an example from somewhere I worked (indirectly) in the late 90s. Nasty bug, easily fixable (a few characters to change). Customer group all p-ed off. Developer has access to the version control server. He changes something on the VC system to appear as if the bug never existed in the version of the code he shipped to whoever. As a result, the bug was deemed to have "mysteriously" appeared somewhere along the line. It didn't help that parts of the workflow were semi-manual, so he *did* have vague things to point at.

I don't believe I can explain that any better or go into details without some risk, so if you don't agree then that's all there is to it.

Suffice it to say I am strongly opposed to the idea, but as long as it's optional -- and for the right reasons (see my other email) -- I'd be OK.