all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Yuan Fu <casouri@gmail.com>
To: Andrea Corallo <acorallo@gnu.org>
Cc: Po Lu <luangruo@yahoo.com>, emacs-devel@gnu.org
Subject: Re: master a4db9b35e16: Merge from savannah/emacs-30
Date: Wed, 7 Aug 2024 21:04:43 -0700	[thread overview]
Message-ID: <E5ED0457-D7AF-4E5F-B13A-619DA3AC9539@gmail.com> (raw)
In-Reply-To: <yp1wmksi581.fsf@fencepost.gnu.org>



> On Aug 7, 2024, at 10:59 AM, Andrea Corallo <acorallo@gnu.org> wrote:
> 
> Yuan Fu <casouri@gmail.com> writes:
> 
>>> On Aug 6, 2024, at 10:51 PM, Po Lu <luangruo@yahoo.com> wrote:
>>> 
>>> Yuan Fu <casouri@gmail.com> writes:
>>> 
>>>> branch: master
>>>> commit a4db9b35e16316a9bec57990a189f774ee165fec
>>>> Merge: 458a79b3c7e cd9a215ef07
>>>> Author: Yuan Fu <casouri@gmail.com>
>>>> Commit: Yuan Fu <casouri@gmail.com>
>>>> 
>>>>   Merge from savannah/emacs-30
>>> 
>>> Going forward, please generate merge commits with `M-x gitmerge' (after
>>> having loaded admin/gitmerge.el).  Thanks.
>> 
>> Sorry. Will do! I was naive to think there isn’t a special process for it :-)
>> 
>> BTW what do you use to reply to a commit and send it to emacs-devel?
> 
> That's the default if one wide replies to a mail on the emacs-diffs
> mailing list, we often discuss commits here this way :)
> 
>  Andrea

Ohhh cool, thanks!




      reply	other threads:[~2024-08-08  4:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <172300708240.29076.13355389322924991771@vcs2.savannah.gnu.org>
     [not found] ` <20240807050444.7124BC1CB0E@vcs2.savannah.gnu.org>
2024-08-07  5:51   ` master a4db9b35e16: Merge from savannah/emacs-30 Po Lu
2024-08-07 15:46     ` Yuan Fu
2024-08-07 17:59       ` Andrea Corallo
2024-08-08  4:04         ` Yuan Fu [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E5ED0457-D7AF-4E5F-B13A-619DA3AC9539@gmail.com \
    --to=casouri@gmail.com \
    --cc=acorallo@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.