git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Bo Yang <struggleyb.nku@gmail.com>
Cc: Jakub Narebski <jnareb@gmail.com>,
	git@vger.kernel.org, Junio Hamano <gitster@pobox.com>
Subject: Re: [PATCH v3 13/13] some document update
Date: Mon, 12 Jul 2010 11:45:31 -0700	[thread overview]
Message-ID: <7v1vb8bktw.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <AANLkTinO9uLByOvUMRf4Y9vcne1jNAfPnvT3Dq0l4xa9@mail.gmail.com> (Bo Yang's message of "Mon\, 12 Jul 2010 22\:12\:57 +0800")

Bo Yang <struggleyb.nku@gmail.com> writes:

> ...
> Thanks a lot for your advice, I have revised the patch.
>
> -----------------------------------------------------------
>>From 88ed88a53d83c2d46fa4917008efadc531ba1068 Mon Sep 17 00:00:00 2001
> From: Bo Yang <struggleyb.nku@gmail.com>
> Date: Sat, 26 Jun 2010 01:35:48 -0700
> Subject: [PATCH v3 revised 13/13] some document update
>
> Both 'git log' and 'git blame' support the same
> format of '-L' arguments, so put the argument
> format description into a new file.
>
> Signed-off-by: Bo Yang <struggleyb.nku@gmail.com>
> ---
>  Documentation/blame-options.txt     |   19 +------------------
>  Documentation/git-log.txt           |   13 +++++++++++++
>  Documentation/line-range-format.txt |   18 ++++++++++++++++++
>  3 files changed, 32 insertions(+), 18 deletions(-)

Every time you do this, you seem to send a corrupt patch, like...

> @@ -19,6 +20,9 @@ command to control what is shown and how, and
> options applicable to
> ...
> diff --git a/Documentation/line-range-format.txt
> b/Documentation/line-range-format.txt

Please don't.

  reply	other threads:[~2010-07-12 18:45 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-11  6:18 [PATCH v3 01/13] parse-options: stop when encounter a non-option Bo Yang
2010-07-11  6:18 ` [PATCH v3 02/13] parse-options: add two helper functions Bo Yang
2010-07-12 16:45   ` Junio C Hamano
2010-07-11  6:18 ` [PATCH v3 03/13] add the basic data structure for line level history Bo Yang
2010-07-12 14:16   ` Bo Yang
2010-07-12 16:50     ` Junio C Hamano
2010-07-18 14:35       ` Bo Yang
2010-07-11  6:18 ` [PATCH v3 04/13] refactor parse_loc Bo Yang
2010-07-12 18:32   ` Junio C Hamano
2010-07-11  6:18 ` [PATCH v3 05/13] parse the -L options Bo Yang
2010-07-13 23:03   ` Junio C Hamano
2010-07-18 14:49     ` Bo Yang
2010-07-19 18:44       ` Junio C Hamano
2010-07-19 22:48         ` Thomas Rast
2010-07-19 23:53           ` Junio C Hamano
2010-07-20  7:51             ` Thomas Rast
2010-07-20 15:45               ` Junio C Hamano
2010-07-22  9:06                 ` Thomas Rast
2010-07-23  2:08                   ` Junio C Hamano
2010-07-20 15:46               ` Bo Yang
2010-07-20 15:47                 ` Bo Yang
2010-07-11  6:18 ` [PATCH v3 06/13] export three functions from diff.c Bo Yang
2010-07-11  6:18 ` [PATCH v3 07/13] add range clone functions Bo Yang
2010-07-12 21:52   ` Junio C Hamano
2010-07-11  6:18 ` [PATCH v3 08/13] map/take range to parent Bo Yang
2010-07-12 21:52   ` Junio C Hamano
2010-07-11  6:18 ` [PATCH v3 09/13] print the line log Bo Yang
2010-07-12 21:52   ` Junio C Hamano
2010-07-11  6:18 ` [PATCH v3 10/13] map/print ranges along traversing the history topologically Bo Yang
2010-07-12 21:52   ` Junio C Hamano
2010-07-11  6:18 ` [PATCH v3 11/13] add --always-print option Bo Yang
2010-07-13 20:35   ` Junio C Hamano
2010-07-11  6:19 ` [PATCH v3 12/13] add two test cases Bo Yang
2010-07-11  6:19 ` [PATCH v3 13/13] some document update Bo Yang
2010-07-11  8:27   ` Jakub Narebski
2010-07-12 14:12     ` Bo Yang
2010-07-12 18:45       ` Junio C Hamano [this message]
2010-07-18 14:37         ` Bo Yang
2010-07-12 16:45 ` [PATCH v3 01/13] parse-options: stop when encounter a non-option Junio C Hamano

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=7v1vb8bktw.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=struggleyb.nku@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).