www-infrastructure-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sam Ruby <ru...@intertwingly.net>
Subject Re: Git, history, protection, and other topics
Date Wed, 04 Nov 2015 16:49:16 GMT
On Wed, Nov 4, 2015 at 9:43 AM, Sam Ruby <rubys@intertwingly.net> wrote:
> On Wed, Nov 4, 2015 at 9:29 AM, Daan Hoogland <daan.hoogland@gmail.com> wrote:
>> On Wed, Nov 4, 2015 at 3:13 PM, Sam Ruby <rubys@intertwingly.net> wrote:
>>
>>> On Wed, Nov 4, 2015 at 8:46 AM, Daan Hoogland <daan.hoogland@gmail.com>
>>> wrote:
>>> > On Wed, Nov 4, 2015 at 2:37 PM, Sam Ruby <rubys@intertwingly.net>
wrote:
>>> >
>>> >> The information that is missing is: "who did the push".
>>> >
>>> > Can we tag any orphaned commits with the commit-id that orphaned them,
>>> for
>>> > maintainer convenience? It will maybe just be for ease of mind but still.
>>>
>>> Doable.
>>>
>>> When a push happens, git will trigger a 'post-receive' hook.
>>> Information that is passed to that hook:  "<before-hash> <after-hash>
>>> <updated-ref>".  A git log command can be used to determine what will
>>> be orphaned (of particular interest is the '...' syntax in
>>> https://git-scm.com/book/en/v2/Git-Internals-Git-References).
>>>
>> I don't see '...' in that link but it figures this is possible.
>
> Bah.  Wrong link.  Here's the correct link:
> https://www.kernel.org/pub/software/scm/git/docs/gitrevisions.html

Found a better solution:

https://github.com/kyanny/git-hooks-detect-force-update

- Sam Ruby

Mime
View raw message