{"thread":{"id":"4176","subject":"[RFC 0/5] Log history of a ref","startedAt":"2006-05-17T09:54:17Z","lastAt":"2006-05-17T09:54:17Z","messageCount":1,"participants":["Shawn Pearce"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"20121","messageId":"20060517095417.GA28529@spearce.org","threadId":"4176","inReplyTo":null,"subject":"[RFC 0/5] Log history of a ref","fromName":"Shawn Pearce","fromEmail":"spearce@spearce.org","sentAt":"2006-05-17T09:54:17Z","receivedAt":"2006-05-17T09:54:17Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"The following 5 [RFC] patches from me are all related to logging\nchanges made to a ref.  These patches contain the same basic idea\nas the two patches I floated earlier this week.  Log files reside\nin .git/logs<ref> and logging is enabled either by creating the\nlog file or by setting 'core.logAllRefUpdates' to true.\n\nSummary is:\n\n * [RFC 1/5] Remove unnecessary local in get_ref_sha1.\n\n\tA minor code cleanup.\n\n * [RFC 2/5] Improve abstraction of ref lock/write.\n\n\tA major reorg of the write_ref_sha1 APIs.  This reorg allows\n\tall internal code to use the same logic for updating any ref,\n\twhich makes it much easier to hook logging in.\n\t\n * [RFC 3/5] Convert update-ref to use ref_lock API.\n\n \tModify update-ref to use the reorg'd write_ref_sha1 API.\n\n * [RFC 4/5] Log ref updates to logs/refs/<ref>\n\n\tAdd logging of refs.  This is the pretty much my latest\n\tlogging patch but cleaned up and built on the above.\n\n * [RFC 5/5] Support 'master@2 hours ago' syntax\n\n\tExtend the SHA1 syntax to search the log for the SHA1 which\n\twas valid at the given point in time.\n\nI still need to fix the receive-pack code to log ref changes prior\nto running the update hook.  I'll probably look at that later this\nweek.  I also need to edit the ~20 sites which call 'git-update-ref'\nto make use of the new \"-m <reason>\" flag.\n\n-- \nShawn.\n"}]}