unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: Stefan Kangas <stefankangas@gmail.com>,  emacs-devel@gnu.org
Subject: Re: master updated (18e7bc87521 -> c71a520d1da)
Date: Wed, 09 Aug 2023 17:16:14 +0800	[thread overview]
Message-ID: <87v8dowp7l.fsf@yahoo.com> (raw)
In-Reply-To: <87leek8ue3.fsf@gmail.com> (Robert Pluim's message of "Wed, 09 Aug 2023 10:58:12 +0200")

Robert Pluim <rpluim@gmail.com> writes:

> You can push a deletion of the feature branch, and then repush the
> rebased branch.

I don't think the 3 or 4 individuals tracking the feature/android branch
would have taken kindly to such a gesture.  (Not merging at all wasn't
an option either, since the branch saw active use.)

Can't the Git people fix this by excluding merge commits from merges
themselves, or something?



  reply	other threads:[~2023-08-09  9:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <169136956945.2149.648813436805504636@vcs2.savannah.gnu.org>
     [not found] ` <CADwFkmmnC9t11ykxg8EJvnqdmtP0VG4xbqRmEiQ8UL6+ZbWvWg@mail.gmail.com>
2023-08-07  2:12   ` master updated (18e7bc87521 -> c71a520d1da) Stefan Kangas
2023-08-07  2:24     ` Stefan Kangas
     [not found]   ` <87wmy737ld.fsf@yahoo.com>
2023-08-07  2:35     ` Po Lu
2023-08-07  2:58       ` Stefan Kangas
2023-08-07  3:52         ` Po Lu
2023-08-09  8:24         ` Robert Pluim
2023-08-09  8:35           ` Po Lu
2023-08-09  8:58             ` Robert Pluim
2023-08-09  9:16               ` Po Lu [this message]
2023-08-09 12:47                 ` Robert Pluim
2023-08-09 11:59           ` Eli Zaretskii

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=87v8dowp7l.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=emacs-devel@gnu.org \
    --cc=rpluim@gmail.com \
    --cc=stefankangas@gmail.com \
    /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).