Question about --tree-filter

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

in working with the "rezip" filter for the efficient git management of
openoffice, zip and docx files, I am encountering the following problem.

Suppose that you have an existing repository and that you want to convert it
into a repository using the rezip filters: git filter-branch should be the tool
to do the conversion.

Initially I believed that once set up the appropriate .git/config filter entries
and a .git/info/attributes file tying the filter to the appropriate file types,
it would have been enough to

git filter-branch --tree-filter true tag-name-filter cat

to do the conversion.
This is also what I suggested in my original post about the rezip script.

Unfortunately, this does not seem to work as expected.  Not all files get
rewritten as filtered blobs.  The only way to do the right job seems to use a
tree-filter that touches every single file in the project.

Any idea why it is so?

Also this is not very nice, because it makes the filter-branch result in a huge
amount of work. In other terms, the rezip blob rewriting gets called many many
times more than needed with this technique.

Does anybody have some suggestion of a tree filter that would be both "safe" and
"efficient" ?

Thanks

Sergio 

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux