On Sat, Aug 8, 2015 at 9:46 PM, Paul Dragoonis <dragoo...@gmail.com> wrote:
> I need someone to turn off the php-webmaster mailer, like now. > > I tried to change author info on commits i've made - which worked fine - > but then blew up the mailer. > > I tested this on other github repositories and was like a transparent > change, all is fine, unless clearly there's a mailer connected to your repo > and it goes nuts. > > Can someone please help!, I'm literally sitting here watching all the > emails rolling in and can't do anything about it :-( > > Many thanks, > Paul > couldn't reach anybody with access to the list server on such a short notice. next time before you do such a thing, or you aren't sure about something, please ask before pushing. usually force pushing to a public repo should be a last resolt for serious stuff like removing copyrighted files or fixing a previous force push. for once, you can destroy history with it, and while it is possible to recover from it (from backups, from reflog before pulling and gc-ing the destroyed history or from a git clone which still have the original state) it can be cumbersome. after a force push other people who are just simply git pulling can end up with diverging local state without understanding what happened (git reset-ing to the origin after fetching solves this), any branch or pull request will be funky when trying to merge it, etc. so please don't blame this on our mail notification system, force pushing 2000+ commit history rewrite shouldn't have happened without prior discussion if at all. Hannes, David, Johannes: what do you think? should we keep the current history (I diffed it and it seems to be the same content, only the commit metadata, author infor was changed) or should we force push the original history (of course for that we should first disable the email notifications in the gitolite config)? -- Ferenc Kovács @Tyr43l - http://tyrael.hu
