git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Andreas Heiduk <asheiduk@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH 2/2] add [--] to usage of filter-branch
Date: Mon, 5 Jun 2017 10:51:09 +0200	[thread overview]
Message-ID: <ef30e8f5-8206-7b42-e229-6cd4b0492e76@gmail.com> (raw)
In-Reply-To: <20170603101755.13619-2-asheiduk@gmail.com>

Am 03.06.2017 um 12:17 schrieb Andreas Heiduk:
> Signed-off-by: Andreas Heiduk <asheiduk@gmail.com>
> ---
>  Documentation/git-filter-branch.txt | 3 ++-
>  git-filter-branch.sh                | 2 +-
>  2 files changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/git-filter-branch.txt b/Documentation/git-filter-branch.txt
> index 45c849d8c..1efdda804 100644
> --- a/Documentation/git-filter-branch.txt
> +++ b/Documentation/git-filter-branch.txt
> @@ -86,7 +86,8 @@ OPTIONS
>  	This is not a real filter executed for each commit but a one
>  	time setup just before the loop. Therefore no commit-specific
>  	variables are defined yet.  Functions or variables defined here
> -	can be used or modified in the following filter steps.
> +	can be used or modified in the following filter steps except
> +	the commit filter, for technical reasons.

I'll move that into the previous commit.

  reply	other threads:[~2017-06-05  8:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-03 10:17 [PATCH 1/2] add setup step to filter-branch Andreas Heiduk
2017-06-03 10:17 ` [PATCH 2/2] add [--] to usage of filter-branch Andreas Heiduk
2017-06-05  8:51   ` Andreas Heiduk [this message]
2017-06-09 13:14     ` Junio C Hamano
2017-06-09 14:33       ` Andreas Heiduk
2017-06-05  2:15 ` [PATCH 1/2] add setup step to filter-branch Junio C Hamano
2017-06-09  5:49   ` Jeff King
2017-06-09 13:11     ` Junio C Hamano
2017-06-10  8:54 ` [PATCH v2 " Andreas Heiduk
2017-06-10  8:54   ` [PATCH v2 2/2] add [--] to usage of filter-branch Andreas Heiduk

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ef30e8f5-8206-7b42-e229-6cd4b0492e76@gmail.com \
    --to=asheiduk@gmail.com \
    --cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).