From: Jay Soffian <jaysoffian@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Confused about diff-tree --cc output
Date: Thu, 5 Feb 2009 03:57:16 -0500 [thread overview]
Message-ID: <76718490902050057u1edb1cffu8f0f8d7cd33f4d42@mail.gmail.com> (raw)
In-Reply-To: <7vmyd1ffcv.fsf@gitster.siamese.dyndns.org>
On Thu, Feb 5, 2009 at 3:38 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Jay Soffian <jaysoffian@gmail.com> writes:
>
>> Is that about right?
>
> Yes, not just about right but it is how it works.
Got it. I did read the thread you pointed me to earlier, but I had to
work through it w/my example to make sure I understood completely. I
appreciate your patience.
j.
prev parent reply other threads:[~2009-02-05 8:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 21:13 Confused about diff-tree --cc output Jay Soffian
2009-02-04 21:56 ` Junio C Hamano
2009-02-05 3:49 ` Jay Soffian
2009-02-05 8:38 ` Junio C Hamano
2009-02-05 8:57 ` Jay Soffian [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=76718490902050057u1edb1cffu8f0f8d7cd33f4d42@mail.gmail.com \
--to=jaysoffian@gmail.com \
--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).