From: Eli Zaretskii <eliz@gnu.org>
To: Federico Tedin <federicotedin@gmail.com>
Cc: 34001@debbugs.gnu.org, tinakellyrussell@gmail.com
Subject: bug#34001: 26.1.90; :distant-foreground face property fails to work in most cases
Date: Fri, 01 Mar 2019 15:48:49 +0200 [thread overview]
Message-ID: <83a7ieiu2m.fsf@gnu.org> (raw)
In-Reply-To: <CAA8GjPnp1+zP=pYxU+6jqYmuH1wtFE1=+u8SBKTg7i493w6Vhw@mail.gmail.com> (message from Federico Tedin on Fri, 1 Mar 2019 09:44:30 -0300)
> From: Federico Tedin <federicotedin@gmail.com>
> Date: Fri, 1 Mar 2019 09:44:30 -0300
> Cc: 34001-done@debbugs.gnu.org, tinakellyrussell@gmail.com
>
> I have a question regarding commit messages and documentation: should I include them in the first iteration
> of the patch I created, or should I wait until there’s been some conversation first? Until now I’ve chosen the
> first option since I’m not always sure the patch I created is correct/applicable/etc.
Please include them with all the iterations, so that whoever ends up
pushing the changes will only need to look at a single email message.
next prev parent reply other threads:[~2019-03-01 13:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 22:31 bug#34001: 26.1.90; :distant-foreground face property fails to work in most cases Tina Russell
2019-01-16 1:08 ` Federico Tedin
2019-01-20 3:20 ` Tina Russell
2019-01-20 17:15 ` Federico Tedin
2019-03-01 8:40 ` Eli Zaretskii
2019-03-01 12:44 ` Federico Tedin
2019-03-01 13:48 ` Eli Zaretskii [this message]
2019-01-21 22:58 ` Basil L. Contovounesios
2019-01-21 23:09 ` Daniel Colascione
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=83a7ieiu2m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=34001@debbugs.gnu.org \
--cc=federicotedin@gmail.com \
--cc=tinakellyrussell@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).