From: "Stefan-W. Hahn" <stefan.hahn@s-hahn.de>
To: "Horst H. von Brand" <vonbrand@inf.utfsm.cl>
Cc: git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: [PATCH] Test for failing pread() on cygwin.
Date: Mon, 8 Jan 2007 18:09:04 +0100 [thread overview]
Message-ID: <20070108170904.GA8086@scotty.home> (raw)
In-Reply-To: <200701080019.l080JW10018679@laptop13.inf.utfsm.cl>
Also sprach Horst H. von Brand am Sun, 07 Jan 2007 at 21:19:32 -0300:
> > +GIT_AUTHOR_EMAIL=xxxxxxxx@yyyyyyyy.yyyyy.yyyyyyy.yyy
>
> Why not the standard "Random J. User" <rju@example.com>? ;-)
Just, because the length of the strings plays a role. With the strings
defined in test_lib there were no errors.
Stefan
--
Stefan-W. Hahn It is easy to make things.
/ mailto:stefan.hahn@s-hahn.de / It is hard to make things simple.
prev parent reply other threads:[~2007-01-08 17:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-06 17:03 problem with git clone on cygwin Stefan-W. Hahn
2007-01-06 21:40 ` Juergen Ruehle
[not found] ` <20070106215919.GB8041@scotty.home>
2007-01-07 9:30 ` Stefan-W. Hahn
2007-01-07 10:46 ` Juergen Ruehle
2007-01-07 11:21 ` Stefan-W. Hahn
2007-01-07 6:00 ` Shawn O. Pearce
2007-01-07 11:17 ` [PATCH] Replacing the system call pread() with real mmap() Stefan-W. Hahn
2007-01-07 11:24 ` Shawn O. Pearce
2007-01-07 16:36 ` Stefan-W. Hahn
2007-01-07 17:10 ` Johannes Schindelin
2007-01-07 20:01 ` Stefan-W. Hahn
2007-01-09 18:51 ` [PATCH] Test for failing pread() on cygwin Stefan-W. Hahn
2007-01-09 18:51 ` [PATCH] Replacing the system call pread() with lseek()/xread()/lseek() sequence Stefan-W. Hahn
2007-01-09 20:21 ` Junio C Hamano
2007-01-07 11:18 ` [PATCH] Test for failing pread() on cygwin Stefan-W. Hahn
2007-01-08 0:19 ` Horst H. von Brand
2007-01-08 17:09 ` Stefan-W. Hahn [this message]
[not found] <11683687161816-git-send-email->
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=20070108170904.GA8086@scotty.home \
--to=stefan.hahn@s-hahn.de \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
--cc=vonbrand@inf.utfsm.cl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.