I already pushed my local commits again, so the history of the warnings plug-in is up to date again.
Am 11.11.2013 um 15:09 schrieb nicolas de loof <nicolas.del...@gmail.com>: > I've pushed plugin's master branches from jenkins.ci.cloudbees.com, > > some of then were rejected, like > g...@github.com:jenkinsci/warnings-plugin.git > > ! [rejected] master -> master (non-fast-forward) > > > Anyway I guess most plugin repo should be restored now. > > > 2013/11/11 Hakan Tandoğan <hakan.tando...@gmail.com> > I pushed transifex-plugin.git from my local tree, all fine for this plugin > now. > > Regards, > Hakan > > > On Sunday, November 10, 2013 7:55:08 PM UTC+1, lucamilanesio wrote: > The solution > > I can raise a request to GitHub to provide the "reflog" of those repositories > and restore the branches to the point before my forced push. > Alternatively the owners of those repositories can still perform a "forced > push" to restore the correct position of the branches. > (if you would like to do so, please write to the mailing list so that we do > not overlap the recovery operations) > > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out.
signature.asc
Description: Message signed with OpenPGP using GPGMail
