From: Mauro Aranda <maurooaranda@gmail.com>
To: Christopher League <league@contrapunctus.net>
Cc: 49274@debbugs.gnu.org
Subject: bug#49274: [PATCH] lisp/cus-theme: retain documentation string when customizing theme
Date: Sat, 03 Jul 2021 10:23:25 -0300 [thread overview]
Message-ID: <87v95rr0oi.fsf@tbb.theblackbeard.org> (raw)
In-Reply-To: <875yxvl7ev.fsf@contrapunctus.net> (message from Christopher League on Wed, 30 Jun 2021 11:05:28 -0400)
Christopher League <league@contrapunctus.net> writes:
> Mauro Aranda <maurooaranda@gmail.com> writes:
>
> Did you send the old one by mistake? Also, please format the commit message
> according to the Emacs conventions: see the file CONTRIBUTE and the “Commit
> messages” section in particular.
>
> Oops yes, sorry for the noise. Attached patch should be better – LMK if it needs anything
> else. Thanks, CL
Thanks, the patch looks good to me.
I'd like to install it, but I'm not sure what are the steps in this
case, regarding the copyright assignment. It doesn't look like a tiny
change, but its mostly indentation: the actual lines changed are 4.
In this case, should I just add a "Copyright-paperwork-exempt: yes"
line? Could someone please confirm, or install the change? Thanks.
next prev parent reply other threads:[~2021-07-03 13:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 14:44 bug#49274: [PATCH] lisp/cus-theme: retain documentation string when customizing theme Christopher League
2021-06-29 22:38 ` Mauro Aranda
2021-06-29 23:54 ` Christopher League
2021-06-30 0:03 ` Mauro Aranda
2021-06-30 1:57 ` Christopher League
2021-06-30 14:09 ` Mauro Aranda
2021-06-30 15:05 ` Christopher League
2021-07-03 13:23 ` Mauro Aranda [this message]
2021-07-03 13:30 ` Lars Ingebrigtsen
2021-07-03 13:52 ` Mauro Aranda
2021-07-03 13:35 ` Eli Zaretskii
2021-07-03 13:55 ` Mauro Aranda
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=87v95rr0oi.fsf@tbb.theblackbeard.org \
--to=maurooaranda@gmail.com \
--cc=49274@debbugs.gnu.org \
--cc=league@contrapunctus.net \
/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).