From: Quy Tonthat <qtonthat@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "Randal L. Schwartz" <merlyn@stonehenge.com>,
"Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: [PATCH] Fix break in git-rev-list.txt
Date: Thu, 23 Aug 2007 02:45:43 +1000 [thread overview]
Message-ID: <46CC6837.6050005@gmail.com> (raw)
In-Reply-To: <7vbqczkhvb.fsf@gitster.siamese.dyndns.org>
Junio C Hamano wrote:
> In any case, I'd appreciate feedbacks from people who recently
> reported formatting breakages on this patch.
I was not aware this problem had been reported/discussed in another
thread (lack of time lately). I would not have had created this
thread otherwise. Sorry for making more noise (than necessary)
and any confusion this may cause.
Anyway, reports/comments will be appreciated.
Quy
prev parent reply other threads:[~2007-08-22 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 8:18 [PATCH] Fix break in git-rev-list.txt Quy Tonthat
2007-08-22 10:01 ` Junio C Hamano
2007-08-22 10:58 ` David Kastrup
2007-08-22 14:37 ` Quy Tonthat
2007-08-22 15:29 ` Quy Tonthat
2007-08-22 16:45 ` Quy Tonthat [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=46CC6837.6050005@gmail.com \
--to=qtonthat@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=merlyn@stonehenge.com \
--cc=spearce@spearce.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;
as well as URLs for NNTP newsgroup(s).