From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Cleanup committed
Date: 04 Dec 1999 02:20:13 +0100 [thread overview]
Message-ID: <m3d7snmrhu.fsf@quimbies.gnus.org> (raw)
I've just done a mop-up of "convention" fixes. That is, I've run
indent-sexp on everything, put double spaces after all full stops in
comments and doc strings, and made all doc strings have a complete
sentence as the first line.
This means that if you're planning on working on bits of the code, you
should check out the latest CVS before doing so. Otherwise, there'll
be lots of conflicts.
*phew* Two years to the next mop-up. :-) Or, if there was a
continual mop done before each release, then this wouldn't be an
issue... Hm. Perhaps I should run the indent-sexp command as part of
the release script? Yes, I think I'll do that.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next reply other threads:[~1999-12-04 1:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-04 1:20 Lars Magne Ingebrigtsen [this message]
1999-12-04 18:07 ` Ben Rogers
1999-12-05 0:17 ` Dave Love
1999-12-05 1:10 ` Lars Magne Ingebrigtsen
1999-12-05 1:12 ` Lars Magne Ingebrigtsen
1999-12-05 1:17 ` Lars Magne Ingebrigtsen
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=m3d7snmrhu.fsf@quimbies.gnus.org \
--to=larsi@gnus.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.
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 NNTP newsgroup(s).