From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <junkio@cox.net>
Cc: Marco Costalba <mcostalba@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 0/3] Fix assorted white space damage
Date: Sun, 13 May 2007 12:31:24 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0705131230230.6410@racer.site> (raw)
In-Reply-To: <7vzm49ts2f.fsf@assigned-by-dhcp.cox.net>
Hi,
On Sat, 12 May 2007, Junio C Hamano wrote:
> In the above I explicitly "saved" t/ because we have some test vectors
> that need to have trailing whitespaces.
AFAICT the documentation has trailing whitespace also, to indicate that
the paragraph does not end here. Correct me if I'm wrong, and these
trailing whitespaces are not necessary.
Ciao,
Dscho
next prev parent reply other threads:[~2007-05-13 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 11:09 [PATCH 0/3] Fix assorted white space damage Marco Costalba
2007-05-12 20:45 ` Junio C Hamano
2007-05-13 3:29 ` Marco Costalba
2007-05-13 1:45 ` Junio C Hamano
2007-05-13 10:31 ` Johannes Schindelin [this message]
2007-05-13 18:57 ` Junio C Hamano
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=Pine.LNX.4.64.0705131230230.6410@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=mcostalba@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 NNTP newsgroup(s).