From: martin rudalics <rudalics@gmx.at>
To: Daniel Koning <dk@danielkoning.com>
Cc: 6130@debbugs.gnu.org
Subject: bug#6130: 23.1; artist-mode spray-can malfunction
Date: Wed, 21 Jan 2015 09:22:22 +0100 [thread overview]
Message-ID: <54BF61BE.5000307@gmx.at> (raw)
In-Reply-To: <m2d269kmh8.fsf@danielkoning.com>
> Okay, but I think this should be a reasonably high priority for the
> maintainers of this part of the lisp tree. Aren't there likely to be
> quite a few undiscovered bugs, some perhaps quite destructive, that
> result from following the behavior as it was documented, just as there
> are (presumably) places where new bugs would manifest if `posnp' were
> brought in line with its advertised behavior? In any case, I've appended
> a FIXME comment in addition to revising the docstring.
Thanks. I slightly tweaked the doc-string of `posnp' to make its first
line fit. We can change the behavior of `posnp' for Emacs 25 as soon as
you received your confirmation from the FSF.
> I added the log entry to the highest-level ChangeLog file, since I
> edited files in lisp/ and doc/ (even though the doc/ changes were only
> in reference to functionality implemented under lisp/). Is that right?
Not really. But the way of writing ChangeLog entries will change in the
near future anyway so there's not much use to tell you the precise
details. I used your entry to create more appropriate ones. I pushed
your changes to the Emacs-24 branch as commit
4c09e3a..3ea1b31 emacs-24 -> emacs-24
They should appear on trunk/master with the next merge. Please have a
look, my experience with git is still rather poor. If you think I've
done everything right, please close the bug.
Thanks, martin
next prev parent reply other threads:[~2015-01-21 8:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 12:17 bug#6130: 23.1; artist-mode spray-can malfunction busk
2015-01-17 5:25 ` Daniel Koning
2015-01-17 13:56 ` martin rudalics
2015-01-18 5:47 ` Daniel Koning
2015-01-18 9:57 ` martin rudalics
2015-01-21 0:26 ` Daniel Koning
2015-01-21 8:22 ` martin rudalics [this message]
2015-01-21 15:22 ` Stefan Monnier
2015-01-21 16:54 ` martin rudalics
2015-01-22 17:02 ` Stefan Monnier
2015-01-22 18:23 ` martin rudalics
2015-01-22 23:08 ` Stefan Monnier
2015-01-23 8:26 ` martin rudalics
2015-01-23 9:43 ` Eli Zaretskii
2015-01-23 16:54 ` martin rudalics
2015-01-23 21:05 ` Stefan Monnier
2015-01-23 21:26 ` Eli Zaretskii
2015-01-23 21:52 ` Daniel Koning
2015-01-24 8:12 ` Eli Zaretskii
2015-01-24 9:08 ` martin rudalics
2015-01-24 9:49 ` Eli Zaretskii
2016-04-06 9:17 ` Johan Busk Eriksson
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=54BF61BE.5000307@gmx.at \
--to=rudalics@gmx.at \
--cc=6130@debbugs.gnu.org \
--cc=dk@danielkoning.com \
/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).