From: Junio C Hamano <junkio@cox.net>
Date: Sun, 14 May 2006 23:14:55 GMT
Subject: Re: Tracking branch history
Message-ID: <7vk68o19n4.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <20060513181816.GA12475@spearce.org>

Shawn Pearce <spearce@spearce.org> writes:

> Log ref updates to logs/refs/<ref>
>
> If config parameter core.logRefUpdates is true then append a line
> to .git/logs/refs/<ref> whenever git-update-ref <ref> is executed.

I cannot decide if a parameter makes more sense, or just making
the existence of such a file a cue is better.  For example, I do
not much care about when I updated each of my topic branch head,
while I do care about master, next, and pu branches.  A global
parameter would make this black-or-white choice, while opening
the log without O_CREAT and write things out only when the log
file exists might make things as easy and controllable.

I could "touch" the ones I care about to prime the process.

Hmm?