From: Michael O'Cleirigh <michael.ocleirigh@rivulet.ca>
To: git@vger.kernel.org
Cc: Michael O'Cleirigh <michael.ocleirigh@rivulet.ca>
Subject: [PATCH 0/1] Add new --index-filter example to git-filter-branch.txt
Date: Wed, 27 Apr 2011 14:08:03 -0400 [thread overview]
Message-ID: <1303927684-6513-1-git-send-email-michael.ocleirigh@rivulet.ca> (raw)
At work I patched git with the prevously sent --egrep-filter patch that allows
an irregular history to be retained, like where code reorganization occured and
you want to keep the history from the original locations.
The comments I recieved at that time was that my case was an --index-filter
variant.
I've reworked it into an --index-filter using the $GIT_COMMIT variable, tested
that it works, and have added it as an example to the git-filter-branch
documentation.
Michael O'Cleirigh (1):
Documentation/git-filter-branch: add --index-filter example
Documentation/git-filter-branch.txt | 13 +++++++++++++
1 files changed, 13 insertions(+), 0 deletions(-)
--
1.7.2.3
next reply other threads:[~2011-04-27 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 18:08 Michael O'Cleirigh [this message]
2011-04-27 18:08 ` [PATCH 1/1] Documentation/git-filter-branch: add --index-filter example Michael O'Cleirigh
2011-04-27 20:32 ` Johannes Sixt
2011-04-27 19:24 ` [PATCH 0/1] Add new --index-filter example to git-filter-branch.txt Sverre Rabbelier
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=1303927684-6513-1-git-send-email-michael.ocleirigh@rivulet.ca \
--to=michael.ocleirigh@rivulet.ca \
--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.
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).