all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mauro Aranda <maurooaranda@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: league@contrapunctus.net, 49274@debbugs.gnu.org
Subject: bug#49274: [PATCH] lisp/cus-theme: retain documentation string when customizing theme
Date: Sat, 03 Jul 2021 10:55:35 -0300	[thread overview]
Message-ID: <87pmvzqz6w.fsf@tbb.theblackbeard.org> (raw)
In-Reply-To: <83h7hbikp9.fsf@gnu.org> (message from Eli Zaretskii on Sat, 03 Jul 2021 16:35:46 +0300)

tags 49274 fixed
close 49274 28.1
quit


Eli Zaretskii <eliz@gnu.org> writes:

>> From: Mauro Aranda <maurooaranda@gmail.com>
>> Date: Sat, 03 Jul 2021 10:23:25 -0300
>> Cc: 49274@debbugs.gnu.org
>> 
>> 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?
>
> Yes, that would have been enough.  However, Christopher has copyright
> assignment on file, so you don't need to add that.  Just install the
> changes under his name as the author.

Thanks Eli.  I installed the change, and I'm closing this bug report.





      reply	other threads:[~2021-07-03 13:55 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
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 [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=87pmvzqz6w.fsf@tbb.theblackbeard.org \
    --to=maurooaranda@gmail.com \
    --cc=49274@debbugs.gnu.org \
    --cc=eliz@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 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.