On Wed, May 20, 2009 at 02:04:58PM -0400, Nicolas Pitre wrote: > > I was envisioning a reflog of tree objects, so you could do: > [...] > Even simpler (for the user) would be to create a full commit with a > synthetic message. The advantage is that the commit would have for > parent the HEAD commit at the moment the operation leading to the reflog > entry was made, with the date tag, etc. The message could even contain I think you are right that this is better. I was trying to save the creation of an extra commit object, but it probably is not that big a deal (as Junio mentioned, we may already be creating multiple tree objects). And having parent information is much richer for doing actual merges of the changes introduced by that reflog commit, not just pulling out individual pieces of its state. So forget my idea of storing trees; it should definitely be commits. -Peff -- 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