From: "Philippe Bruhat (BooK)" <philippe.bruhat@free.fr>
To: "Philippe Bruhat (BooK)" <book@cpan.org>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] Git.pm: let a false Directory parameter (such as 0) be used correctly by the constructor
Date: Fri, 2 Jan 2009 10:09:40 +0100 [thread overview]
Message-ID: <20090102090940.GA23222@plop> (raw)
In-Reply-To: <1230886057-23994-1-git-send-email-book@cpan.org>
On Fri, Jan 02, 2009 at 09:47:37AM +0100, Philippe Bruhat (BooK) wrote:
> Signed-off-by: Philippe Bruhat (BooK) <book@cpan.org>
> ---
> perl/Git.pm | 7 ++++---
> 1 files changed, 4 insertions(+), 3 deletions(-)
Please ignore, I forgot half of the the requested changes. Sorry for the
noise.
--
Philippe Bruhat (BooK)
Mankind is the story of the same mistakes in different places.
(Moral from Groo #1 (Image))
prev parent reply other threads:[~2009-01-02 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 8:47 [PATCH] Git.pm: let a false Directory parameter (such as 0) be used correctly by the constructor Philippe Bruhat (BooK)
2009-01-02 9:09 ` Philippe Bruhat (BooK) [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=20090102090940.GA23222@plop \
--to=philippe.bruhat@free.fr \
--cc=book@cpan.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).