unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Alan Third <alan@idiocy.org>
Cc: Carlos Pita <carlosjosepita@gmail.com>, 37756@debbugs.gnu.org
Subject: bug#37756: [PATCH] Wrong initialization of fringe bitmap
Date: Thu, 17 Oct 2019 17:01:54 +0200	[thread overview]
Message-ID: <m27e531km5.fsf@gmail.com> (raw)
In-Reply-To: <20191017115351.GB11160@breton.holly.idiocy.org> (Alan Third's message of "Thu, 17 Oct 2019 12:53:51 +0100")

>>>>> On Thu, 17 Oct 2019 12:53:51 +0100, Alan Third <alan@idiocy.org> said:

    Alan> On Wed, Oct 16, 2019 at 05:01:11PM -0300, Carlos Pita wrote:
    >> > Use one of the related Emacs commands, and Emacs will do that for you.
    >> > Those commands are described in CONTRIBUTE under "Generating ChangeLog
    >> > entries".
    >> 
    >> I'm having some issues doing that because I'm using magit to amend /
    >> reword previously committed changes, so the instructions there don't
    >> quite match my situation. Will try harder later, for now I just
    >> modified the message after some examples in your git log. Hope it's ok
    >> now.

    Alan> In the Magit diff view that is displayed when comitting you should be
    Alan> able to just hit ‘C’ with point in the code you want to add to the
    Alan> commit message.

That doesnʼt auto-snarf the function names the way C-x 4 A or C-c C-w
do in vc.

Robert





  reply	other threads:[~2019-10-17 15:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-15  2:39 bug#37756: [PATCH] Wrong initialization of fringe bitmap Carlos Pita
2019-10-15  9:47 ` Eli Zaretskii
2019-10-15 10:14   ` Carlos Pita
2019-10-16 17:28     ` Carlos Pita
2019-10-16 18:35       ` Eli Zaretskii
2019-10-16 18:54         ` Carlos Pita
2019-10-16 19:05           ` Eli Zaretskii
2019-10-16 20:01             ` Carlos Pita
2019-10-17 11:53               ` Alan Third
2019-10-17 15:01                 ` Robert Pluim [this message]
2019-10-26 10:21               ` 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=m27e531km5.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=37756@debbugs.gnu.org \
    --cc=alan@idiocy.org \
    --cc=carlosjosepita@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).