From: Noah Friedman <noah@splode.com>
To: emacs-devel@gnu.org
Subject: Re: oops
Date: Mon, 08 May 2017 17:13:03 -0700 (PDT) [thread overview]
Message-ID: <20170508171303.215891.FMU2863@unexploded-cow.prv.splode.com> (raw)
>I fat-fingered "git push --all" (bad habit from work) when pushing a single
>change I made on the emacs-25 branch, and I fear I may have restored some
>branch tags that had been renamed or deleted upstream. Many apologies.
Ok, actually as far as I can tell no branches were modified, but the server
generated a whole slew of diffs for changes that were already there, and I
don't understand why. Apologies still.
next reply other threads:[~2017-05-09 0:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 0:13 Noah Friedman [this message]
2017-05-09 2:52 ` oops Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170508171303.215891.FMU2863@unexploded-cow.prv.splode.com \
--to=noah@splode.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).