From: Ben Rogers <brogers@columbus.rr.com>
Subject: Re: Cleanup committed
Date: 04 Dec 1999 13:07:17 -0500 [thread overview]
Message-ID: <h0d7sminqi.fsf@dhcp9538171.columbus.rr.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "04 Dec 1999 02:20:13 +0100"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> *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.
I worked for a company which forced indentation checks as a part of
the CVS commit checking. While this is a little draconian it does
mean that there aren't any monstrous changes for re-indentation.
As long as you can run indent-sexp from the command line, it is pretty
simple to integrate into the CVS commit script.
ben
--
PGP Key fingerprint = 6A1B 3972 16F9 20E8 9F61 CCA3 AC38 7C55 EA00 89BE
next prev parent reply other threads:[~1999-12-04 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-04 1:20 Lars Magne Ingebrigtsen
1999-12-04 18:07 ` Ben Rogers [this message]
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=h0d7sminqi.fsf@dhcp9538171.columbus.rr.com \
--to=brogers@columbus.rr.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.
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).