From: Lute Kamstra <Lute.Kamstra.lists@xs4all.nl>
To: Glenn Morris <rgm@gnu.org>
Cc: Juanma Barranquero <lekktu@gmail.com>, emacs-devel@gnu.org
Subject: Re: Leading * in docstrings of defcustoms.
Date: Tue, 25 Nov 2008 06:50:05 +0100 [thread overview]
Message-ID: <878wr89wxe.fsf@speer.lan> (raw)
In-Reply-To: <e5wsetd0hr.fsf@fencepost.gnu.org> (Glenn Morris's message of "Mon, 24 Nov 2008 02:52:32 -0500")
Glenn Morris <rgm@gnu.org> writes:
> "Juanma Barranquero" wrote:
>
>> It should be OK for packages that are not independently maintained
>> outside of Emacs (like org, tramp, etc.).
>
> I was going to say, why should that make a difference - they must all
> have come up with ways to do "automatic" syncs by now, or gone crazy.
> But in light of recent events, maybe not! :)
(Unfortunately, I don't read emacs-devel actively enough to know what
recent events you are referring to to.)
Is there a list of lisp files that are maintained outside of Emacs? If
not, could someone compile it and put it in admin/?
>> But such a large scale change is likely to piss off people with many
>> local changes in their workspaces.
>
> Only if it causes conflicts. I doubt there are many people with lots
> of uncommitted changes to doc-strings (or close by).
>
> I'd like to see the "*"s removed. And if it were done when 'tis done,
> then 'twere well it were done quickly...
I think any merge conflict involving a removed * is easily resolved by
hand.
Lute.
next prev parent reply other threads:[~2008-11-25 5:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 19:31 Leading * in docstrings of defcustoms Lute Kamstra
2008-11-22 22:00 ` Juanma Barranquero
2008-11-24 7:52 ` Glenn Morris
2008-11-24 8:31 ` Juanma Barranquero
2008-11-24 16:02 ` Stefan Monnier
2008-11-24 16:55 ` Drew Adams
2008-11-24 20:36 ` Chong Yidong
2008-11-24 22:43 ` Drew Adams
2008-11-24 23:21 ` Chong Yidong
2008-11-24 17:48 ` Stephen J. Turnbull
2008-11-25 5:50 ` Lute Kamstra [this message]
2008-11-28 12:48 ` Lute Kamstra
2008-11-28 12:58 ` Juanma Barranquero
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=878wr89wxe.fsf@speer.lan \
--to=lute.kamstra.lists@xs4all.nl \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=rgm@gnu.org \
/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.