From: Noam Postavsky <npostavs@gmail.com>
To: Pierre Lorenzon <devel@pollock-nageoire.net>
Cc: 32564@debbugs.gnu.org, cedet-devel@lists.sourceforge.net
Subject: bug#32564: 27.0.50; cedet/ede/pconf.el
Date: Sun, 16 Sep 2018 20:39:47 -0400 [thread overview]
Message-ID: <87pnxdq7n0.fsf@gmail.com> (raw)
In-Reply-To: <20180901.053858.756858765859300250.devel@pollock-nageoire.net> (Pierre Lorenzon's message of "Sat, 01 Sep 2018 05:38:58 +0200 (CEST)")
tags 32564 fixed
close 32564
quit
Pierre Lorenzon <devel@pollock-nageoire.net> writes:
> In my opinion your solution is clearly better than the small
> dirthy hack I have done ! But I am developer of none of these
> packages, so I have simply done the simplest and fastest
> thing I could do to be able using C-c . C to compile my codes
> !
Unfortunately, I don't think there are any (active) developers of these
packages. I've pushed your patch since it's obviously better than what
we have now, and added a FIXME note about improving this.
P.S. you're getting somewhat close to the limit of unassigned changes
(which is approximately 15 lines). Would you consider assigning
copyright for Emacs? There is a form at
https://git.savannah.gnu.org/cgit/gnulib.git/tree/doc/Copyright/request-assign.future
[1: b2c1b03f6b]: 2018-09-16 20:25:44 -0400
Update pconf for compile.el mode-line-process changes
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=b2c1b03f6ba1fbf0514bd51dfbbc36d202d0c807
[2: bc4f4b6e0c]: 2018-09-16 20:25:44 -0400
; Add FIXME regarding previous change
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=bc4f4b6e0ccbc361f4fabbed5eb2e5a357107588
prev parent reply other threads:[~2018-09-17 0:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 3:28 bug#32564: 27.0.50; cedet/ede/pconf.el Pierre Lorenzon
2018-09-01 2:16 ` Noam Postavsky
2018-09-01 3:38 ` Pierre Lorenzon
2018-09-17 0:39 ` Noam Postavsky [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
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=87pnxdq7n0.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=32564@debbugs.gnu.org \
--cc=cedet-devel@lists.sourceforge.net \
--cc=devel@pollock-nageoire.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).