unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Comments vs. commit log
Date: Wed, 28 Sep 2011 10:21:12 +0200	[thread overview]
Message-ID: <87r531w007.fsf@pobox.com> (raw)
In-Reply-To: <87k48togvo.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 27 Sep 2011 22:43:55 +0200")

On Tue 27 Sep 2011 22:43, ludo@gnu.org (Ludovic Courtès) writes:

> Would it be possible to move the explanations from the commit log to
> comments in the code?
>
> Looking at the above code, I have no idea what a var-table or a counter
> is, what it’s used for, etc.

Sure.  I forget sometimes, because I've read that Waddell & Dybvig paper
so many times that I forget it's not written down in the source ;)

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2011-09-28  8:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1R86pF-00043N-0v@vcs.savannah.gnu.org>
2011-09-27 20:43 ` Comments vs. commit log Ludovic Courtès
2011-09-28  8:21   ` Andy Wingo [this message]
2011-09-30 12:48     ` Ludovic Courtès

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/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r531w007.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@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.
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).