unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ken Manheimer <ken.manheimer@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 42218@debbugs.gnu.org
Subject: bug#42218: 28.0.50; Fix for missed item undecoration on allout-widgets-mode deactivation
Date: Tue, 21 Jul 2020 11:17:36 -0400	[thread overview]
Message-ID: <CAAT_zTHDpvnf8_b=S=ZqaC01ys5mY3ZcMjF3YewNfMd0-g6tGQ@mail.gmail.com> (raw)
In-Reply-To: <83eep5hag8.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]

Ok, reverts of the emacs-27 backports are pushed to origin.

On Mon, Jul 20, 2020 at 10:24 PM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Ken Manheimer <ken.manheimer@gmail.com>
> > Date: Mon, 20 Jul 2020 16:09:51 -0400
> > Cc: 42218@debbugs.gnu.org
> >
> > In my local checkout of the emacs-27 branch I have reversal of the five
> commits ready to push upstream. I'm
> > sorry to bother you further with this, but rather than risk compounding
> the problem I want to double-check
> > that reversing the commits (rather than, eg, reversing the changes in
> new commits) is the right way to go,
> > before I push upstream. I know that this is a different situation than
> to problem-prone one of doing a reset
> > and pushing that, but haven't pushed reversed commits and want to be
> sure. (This time I will wait for your
> > reply rather than just going ahead.)
>
> The right way is to say "git revert SHA1" for each of the commits you
> want to revert.  This creates a commit with reverse diffs.  Then "git
> push" the result.
>
> Thanks.
>

[-- Attachment #2: Type: text/html, Size: 1543 bytes --]

  reply	other threads:[~2020-07-21 15:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-05 21:04 bug#42218: 28.0.50; Fix for missed item undecoration on allout-widgets-mode deactivation Ken Manheimer
2020-07-18  7:43 ` Eli Zaretskii
2020-07-20 17:56   ` Ken Manheimer
2020-07-20 18:38     ` Eli Zaretskii
2020-07-20 18:58       ` Ken Manheimer
2020-07-20 19:24         ` Eli Zaretskii
2020-07-20 19:28           ` Eli Zaretskii
2020-07-20 20:09             ` Ken Manheimer
2020-07-21  2:24               ` Eli Zaretskii
2020-07-21 15:17                 ` Ken Manheimer [this message]
2020-07-21 16:34                   ` Eli Zaretskii
     [not found] ` <handler.42218.B.159398312421153.ack@debbugs.gnu.org>
2020-07-20 19:15   ` bug#42218: Acknowledgement (28.0.50; Fix for missed item undecoration on allout-widgets-mode deactivation) Ken Manheimer

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='CAAT_zTHDpvnf8_b=S=ZqaC01ys5mY3ZcMjF3YewNfMd0-g6tGQ@mail.gmail.com' \
    --to=ken.manheimer@gmail.com \
    --cc=42218@debbugs.gnu.org \
    --cc=eliz@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).