unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Amin Bandali <bandali@gnu.org>
Cc: emacs-erc@gnu.org, 44100@debbugs.gnu.org,
	Olivier Certner <ocert.dev@free.fr>
Subject: bug#44100: 26.3; ERC: Make IBuffer custom display work again
Date: Fri, 04 Jun 2021 12:07:51 +0200	[thread overview]
Message-ID: <87v96ux7rc.fsf_-___19953.2086773374$1622801630$gmane$org@gnus.org> (raw)
In-Reply-To: <87pn4pusiy.fsf@gnu.org> (Amin Bandali's message of "Sat, 07 Nov 2020 09:54:13 -0500")

Amin Bandali <bandali@gnu.org> writes:

> 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.

Amin, Olivier's paperwork is now complete, so could you look at the
following four patches from Olivier and review (and possibly apply)?

46777 normal,pat Olivier Certner    28.0.50; ERC: NickServ identification: Prompt for password after other sources, overall simplifications
46775 normal,pat Olivier Certner    27.1; ERC: Track: Modified channels doc and `erc-track-find-face' fixes
44140 normal,pat Olivier Certner    26.3; ERC stamps: Really use latest buffer's window's width prior to `fill-column'
44100 normal,pat Olivier Certner    26.3; ERC: Make IBuffer custom display work again


-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-06-04 10:07 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
2021-06-04 10:07                 ` Lars Ingebrigtsen [this message]
     [not found]                 ` <87v96ux7rc.fsf_-_@gnus.org>
2021-06-04 19:58                   ` bug#44100: 26.3; ERC: Make IBuffer custom display work again 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='87v96ux7rc.fsf_-___19953.2086773374$1622801630$gmane$org@gnus.org' \
    --to=larsi@gnus.org \
    --cc=44100@debbugs.gnu.org \
    --cc=bandali@gnu.org \
    --cc=emacs-erc@gnu.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).