From: "Jay Soffian" <jaysoffian@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Robert Shearman" <robertshearman@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH 1/4] git-imap-send: Allow the program to be run from subdirectories of a git tree.
Date: Tue, 8 Jul 2008 21:28:03 -0400 [thread overview]
Message-ID: <76718490807081828k7640d07bp547a69d05a6e07c4@mail.gmail.com> (raw)
In-Reply-To: <7v3amjq2mj.fsf@gitster.siamese.dyndns.org>
On Tue, Jul 8, 2008 at 9:15 PM, Junio C Hamano <gitster@pobox.com> wrote:
> I thought Jeff already explained why this NULL was a bad idea, but perhaps
> I was dreaming...
http://article.gmane.org/gmane.comp.version-control.git/87701
j.
next prev parent reply other threads:[~2008-07-09 1:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 22:18 [PATCH 1/4] git-imap-send: Allow the program to be run from subdirectories of a git tree Robert Shearman
2008-07-09 1:15 ` Junio C Hamano
2008-07-09 1:28 ` Jay Soffian [this message]
2008-07-09 12:08 ` Rob Shearman
-- strict thread matches above, loose matches on Subject: below --
2008-07-09 21:28 Robert Shearman
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=76718490807081828k7640d07bp547a69d05a6e07c4@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=robertshearman@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).