From: Amin Bandali <bandali@gnu.org>
To: Olivier Certner <ocert.dev@free.fr>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
emacs-erc@gnu.org, bug-gnu-emacs@gnu.org, 44100@debbugs.gnu.org
Subject: Re: bug#44100: Patch
Date: Sat, 07 Nov 2020 09:54:13 -0500 [thread overview]
Message-ID: <87pn4pusiy.fsf@gnu.org> (raw)
In-Reply-To: <1779714.fmOJIAR8ZY@ravel>
[-- Attachment #1: Type: text/plain, Size: 1377 bytes --]
Hi Olivier,
Olivier Certner writes:
> Hello Amin,
>
> Sorry for the late reply, I missed these mails in a flood of other mails.
>
No problem!
>
> And sorry as well for the ChangeLog entry, I had read CONTRIBUTE, but
> mixed things up (there is a section explaining how to generate change
> log entries in Emacs afterwards, and I forgot the earlier advice).
>
Ah :-). No worries; I thought I'd point out CONTRIBUTE just in case
you'd missed it.
>
>> [...]
>>
>> I welcome anyone who would like to volunteer to send a patch for
>> updating those functions to work with a normalized list of lists for
>> those two variables, granted they can provide a convincing argument that
>> their change is correct and does not break the current behaviour, does
>> not dramatically further increase the complexity of the algorithms, and
>> is ideally backward compatible with the current non-normalized structure
>> of those two variables as well.
>
> I'll have a look at this next week.
>
> Thanks and regards.
Sounds good, thanks! Please keep us updated on how it goes.
Also, since implementing this will likely cross the ~15 line triviality
threshold, I sent you a copy of the copyright assignment request form
off-list, which you would fill out and send to the copyright clerk to
start the process of assigning the copyright for your changes to Emacs
to the FSF.
Thanks,
amin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 857 bytes --]
next prev parent reply other threads:[~2020-11-07 14:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 16:39 bug#44100: 26.3; ERC: Make IBuffer custom display work again Olivier Certner
2020-10-21 10:08 ` bug#44100: Patch Olivier Certner
2020-10-21 15:54 ` Corwin Brust
[not found] ` <CAJf-WoRBf-TNXSopiUnugOgAj_GAnJsRjkbuwBXRc-m4EB7-Jw@mail.gmail.com>
2020-10-31 19:54 ` Amin Bandali
[not found] ` <87imaquq6z.fsf@gnu.org>
2020-11-01 2:16 ` Amin Bandali
[not found] ` <875z6pu8h5.fsf@gnu.org>
2020-11-01 13:09 ` Lars Ingebrigtsen
[not found] ` <87mu01cjfh.fsf@gnus.org>
2020-11-03 2:38 ` Amin Bandali
[not found] ` <87lffjf9lu.fsf@gnu.org>
2020-11-05 16:38 ` Olivier Certner
2020-11-07 14:54 ` Amin Bandali [this message]
2021-06-04 10:07 ` bug#44100: 26.3; ERC: Make IBuffer custom display work again Lars Ingebrigtsen
[not found] ` <87v96ux7rc.fsf_-_@gnus.org>
2021-06-04 19:58 ` bandali
[not found] ` <1946874.pO33bOzxCm@ravel>
2021-08-03 2:52 ` Amin Bandali
2021-07-06 12:06 ` bug#44100: Updated patch Olivier Certner
2021-07-06 14:29 ` bug#44100: On Amin's proposed change Olivier Certner
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=87pn4pusiy.fsf@gnu.org \
--to=bandali@gnu.org \
--cc=44100@debbugs.gnu.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=emacs-erc@gnu.org \
--cc=larsi@gnus.org \
--cc=ocert.dev@free.fr \
/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).