Re: [Tails-dev] Heads up! Git history has been rewritten, *…

Delete this message

Reply to this message
Author: bertagaz
Date:  
To: The Tails public development discussion list
New-Topics: Re: [Tails-dev] updating doc wrt. commit name and email [Was: Heads up! Git history has been rewritten ...]
Subject: Re: [Tails-dev] Heads up! Git history has been rewritten, *you* have to do something [Was: Rewriting the Git repository]
On Wed, Feb 25, 2015 at 06:57:16PM +0100, intrigeri wrote:
> Hi,
>
> Non-Git-committers can skip what follows, but Git committers should
> probably read it.
>
> Note that Git hooks have been set up so that we should *not* be able
> to mistakenly push obsolete, deleted tags (jenkins-*..) nor any branch
> or other kind of ref that contains any commit from the old history.
>
> And while we were at it, the same hooks also prevent us from
> mistakenly pushing unannotated (unsigned) Git tags, since they're
> a real pain to deal with on the infra side of things (e.g. one cannot
> ensure they propagate correctly once rewritten, among other problems).
>
> If you have ideas of other fail-safe protections we could add there,
> cool, let's discuss that! (in a dedicated thread, though)


Also note that this might be the right time while reconfiguring your git
to remove the old common `user.name` and `user.email` git config we used, as
we decided recently to get rid of that. :)

bert.