git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[DOC PATCH] State the effect of filter-branch on graft explicitly

From
Daniel Cheng (aka SDiZ) <j16sdiz+freenet@gmail.com>
Date
Apr 10, 2009, 06:26 UTC
Message-ID
<1239344809-4451-1-git-send-email-j16sdiz+freenet@gmail.com>
Signed-off-by: Daniel Cheng (aka SDiZ) <j16sdiz+freenet@gmail.com>
---

The documentation state nothing about effect of graft in filter-branch. The only (implicit) reference is the "simplier" method in the example section.

This patch make the reference explicit.
 Documentation/git-filter-branch.txt |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-filter-branch.txt b/Documentation/git-filter-branch.txt
index 237f85e..e281290 100644
--- a/Documentation/git-filter-branch.txt
+++ b/Documentation/git-filter-branch.txt
@@ -31,6 +31,9 @@ changes, which would normally have no effect.  Nevertheless, this may be
 useful in the future for compensating for some git bugs or such,
 therefore such a usage is permitted.
 
+*NOTE*: This command honor `.git/info/grafts`. If you have any grafts
+defined, running this command will make them permanent.
+
 *WARNING*! The rewritten history will have different object names for all
 the objects and will not converge with the original branch.  You will not
 be able to easily push and distribute the rewritten branch on top of the
-- 
1.6.2.1
Next: Sverre Rabbelier
Message 1 of 2 in “State the effect of filter-branch on graft explicitly”
  1. State the effect of filter-branch on graft explicitlyDaniel Cheng (aka SDiZ), Apr 10, 2009
  2. Sverre RabbelierApr 10, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.