On Tue, Oct 11, 2011 at 02:31:48PM -0700, Junio C Hamano wrote: > Jeff King <peff@xxxxxxxx> writes: > > > But in the code, it is spelled RENAMED-REF (with a dash). And as far as > > I can tell, does not actually create a reflog. And it's not documented > > anywhere, so I suspect nobody is using it. Maybe it is worth switching > > that name. > > Or even better get rid of it? Fine by me. I'm not sure anyone is even aware that it exists. Just to double-check, I grepped the list archives, and the biggest mention of it was its presence causing a weird bug: http://thread.gmane.org/gmane.comp.version-control.git/143737 Googling turns up only confusion, nobody actually using it or recommending that it be used. OTOH, it does actually serialize branch renames, since we take a lock on it. Maybe that's important. Cc'ing Lars. Certainly renaming it would be the conservative choice. -Peff PS I mentioned above that it does not actually create a reflog. Digging in the code more, I think it is capable of it, but my git.git clone had RENAMED-REF, but no reflog. I would have thought core.logAllRefUpdates would turn it on, but maybe there is a funny interaction with things not in refs/. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html