From: Sean <seanlkml@sympatico.ca>
To: "Marco Costalba" <mcostalba@gmail.com>
Cc: "Alex Riesen" <raa.lkml@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [PATCH] Add --show-size to git log to print message size
Date: Sun, 15 Jul 2007 12:16:00 -0400 [thread overview]
Message-ID: <20070715121600.792982ef.seanlkml@sympatico.ca> (raw)
In-Reply-To: <e5bfff550707150858i1825e01clf0897ad4db319373@mail.gmail.com>
On Sun, 15 Jul 2007 17:58:21 +0200
"Marco Costalba" <mcostalba@gmail.com> wrote:
> What should I search for to find the revision boundary? "\n\0" ? is
> this that you mean with ^\0
Essentially yes. That pattern will never appear inside the comment
or patch text because both sections are always indented. So in the
example you cite, "\n\0" would match the proper terminator, and the
"\n-\0" NUL would be ignored.
Sean
next prev parent reply other threads:[~2007-07-15 16:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-14 16:52 [PATCH] Add --show-size to git log to print message size Marco Costalba
2007-07-14 19:03 ` Junio C Hamano
2007-07-14 20:46 ` Marco Costalba
2007-07-15 9:35 ` Alex Riesen
2007-07-15 10:06 ` Marco Costalba
2007-07-15 10:48 ` Alex Riesen
2007-07-15 11:32 ` Marco Costalba
2007-07-15 12:29 ` Marco Costalba
2007-07-15 12:35 ` Sean
2007-07-15 14:58 ` Marco Costalba
2007-07-15 15:04 ` Sean
2007-07-15 15:58 ` Marco Costalba
2007-07-15 16:16 ` Sean [this message]
2007-07-15 16:27 ` Marco Costalba
2007-07-15 16:34 ` Sean
2007-07-15 16:54 ` Marco Costalba
2007-07-15 18:14 ` Linus Torvalds
2007-07-15 18:45 ` Marco Costalba
2007-07-16 12:04 ` Marco Costalba
2007-07-16 12:31 ` Alex Riesen
2007-07-16 17:50 ` Junio C Hamano
2007-07-16 17:55 ` Marco Costalba
2007-07-16 18:02 ` Marco Costalba
2007-07-16 22:37 ` Junio C Hamano
2007-07-16 17:50 ` Marco Costalba
2007-07-17 7:49 ` Andy Parkins
2007-07-17 16:36 ` Marco Costalba
2007-07-25 4:03 ` Junio C Hamano
2007-07-25 9:38 ` Marco Costalba
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=20070715121600.792982ef.seanlkml@sympatico.ca \
--to=seanlkml@sympatico.ca \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mcostalba@gmail.com \
--cc=raa.lkml@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).