git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Vilain <sam@vilain.net>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
	Git Mailing List <git@vger.kernel.org>,
	Johannes Sixt <johannes.sixt@telecom.at>
Subject: Re: [mingw port] git plumbing piping with CR/NL
Date: Sat, 02 Jun 2007 13:31:57 +1200	[thread overview]
Message-ID: <4660C88D.2010208@vilain.net> (raw)
In-Reply-To: <20070601231816.GC6360@steel.home>

Alex Riesen wrote:
> > Apparently git should ignore \r at the end of the path. ...
> Why should it? \r is a valid character in filenames almost everywhere
> (except for the some proprietary OSes, as usual).
>   

So is \n!

Sam.

      parent reply	other threads:[~2007-06-02  1:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-01 18:23 [mingw port] git plumbing piping with CR/NL Nguyen Thai Ngoc Duy
2007-06-01 23:18 ` Alex Riesen
2007-06-01 23:56   ` Nguyen Thai Ngoc Duy
2007-06-02  1:31     ` Johannes Schindelin
2007-06-02 23:09     ` Alex Riesen
2007-06-02  1:31   ` Sam Vilain [this message]

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=4660C88D.2010208@vilain.net \
    --to=sam@vilain.net \
    --cc=git@vger.kernel.org \
    --cc=johannes.sixt@telecom.at \
    --cc=pclouds@gmail.com \
    --cc=raa.lkml@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).