unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: No Itisnt <theseaisinhere@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org, No Itisnt <theseaisinhere+git@gmail.com>
Subject: Re: [Guile-commits] GNU Guile branch, master, updated.  release_1-9-11-164-gd26a26f
Date: Sun, 11 Jul 2010 19:19:56 -0500	[thread overview]
Message-ID: <AANLkTilwAwxipFCHMNidcYAbQTHN71FzPTruiMAAZ-2v@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimndUygYxcwL1__QXMmUX4154b8t9_VLhHr2xn3@mail.gmail.com>

See "[PATCH] Allow printing of malformed tree-il"

On Sun, Jul 11, 2010 at 7:09 PM, No Itisnt <theseaisinhere@gmail.com> wrote:
> Hi, yes that was part of a patch Andy approved but I never committed
> the second part due to issues.
>
> On Sun, Jul 11, 2010 at 5:55 PM, Ludovic Courtès <ludo@gnu.org> wrote:
>> Hi!
>>
>> "No Itisnt" <theseaisinhere+git@gmail.com> writes:
>>
>>> commit d26a26f6c0fbdb971995d1b3dcf3345831eb12d7
>>> Author: No Itisnt <theseaisinhere+git@gmail.com>
>>> Date:   Fri Jul 9 21:22:27 2010 -0500
>>>
>>>     Remove trailing whitespace
>>>
>>>     * module/language/tree-il.scm: Remove trailing whitespace
>>
>> Unless you have an explicit OK, please avoid commits “just” to remove
>> whitespace.
>>
>> I think people on this list had +/- agreed that trailing whitespaces are
>> Bad(TM), and that we would avoid them (e.g., using an Emacs hook), but
>> that we could nonetheless live with them and would avoid whitespace
>> commits.
>>
>> Thanks,
>> Ludo’.
>>
>



  reply	other threads:[~2010-07-12  0:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1OXPjX-0000lG-6v@vcs-noshell.in.savannah.gnu.org>
2010-07-11 22:55 ` [Guile-commits] GNU Guile branch, master, updated. release_1-9-11-164-gd26a26f Ludovic Courtès
2010-07-12  0:09   ` No Itisnt
2010-07-12  0:19     ` No Itisnt [this message]
2010-07-12 12:01     ` 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=AANLkTilwAwxipFCHMNidcYAbQTHN71FzPTruiMAAZ-2v@mail.gmail.com \
    --to=theseaisinhere@gmail.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=theseaisinhere+git@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).