www-infrastructure-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daan Hoogland <daan.hoogl...@gmail.com>
Subject Re: Git, history, protection, and other topics
Date Wed, 04 Nov 2015 14:29:37 GMT
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. ​

​It will help maintainers and reduce the need to limit --force karma.​



> Related: here is progress towards a GitHub multimail hook:
>
> https://github.com/git-multimail/git-multimail/issues/109#issuecomment-153022717

​so is your intention to with gitmultimail related to closing --force
rights?​


>
>
> - Sam Ruby
>



-- 
Daan

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message