Git development
 help / color / mirror / Atom feed
From: "Stefan Näwe" <stefan.naewe+git@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Fix t7606 on Cygwin: for some reasont it does not recognize a "." in PATH
Date: Fri, 12 Dec 2008 14:01:14 +0000 (UTC)	[thread overview]
Message-ID: <loom.20081212T135919-571@post.gmane.org> (raw)
In-Reply-To: 81b0412b0812120428mc85ae84r260b722022dc3449@mail.gmail.com

Alex Riesen <raa.lkml <at> gmail.com> writes:

> 
> The test uses the dot to add custom merge strategies
> ---
>  t/t7606-merge-custom.sh |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> Attachment (0001-Fix-t7606-on-Cygwin-it-does-not-recognize-a-.-in.patch): 
application/octet-stream, 759 bytes

Any special reason why you sent this as an (normally frowned-upon) attachment ?

For me, however, this would be the way to go to be able to download the patch 
without any hassle. (see my other post).

Regards,
  Stefan

      reply	other threads:[~2008-12-12 14:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-12 12:29 [PATCH] Fix t7606 on Cygwin: for some reasont it does not recognize a "." in PATH Alex Riesen
2008-12-12 14:01 ` Stefan Näwe [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=loom.20081212T135919-571@post.gmane.org \
    --to=stefan.naewe+git@gmail.com \
    --cc=git@vger.kernel.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