David Tweed schrieb: > $ git filter-branch --subdirectory-filter WRITING/ HEAD > Rewrite 42f24be8d8198738134a19471697b39359199fa3 (351/351) > Ref 'refs/heads/master' was rewritten > > $ git rev-list HEAD | wc > 55 55 2255 > ... > > Digging a little into the shell-script I find the list of commits is > generated with > > git rev-list --reverse --topo-order --default HEAD --parents HEAD > --full-history -- WRITING > > and (adding --pretty so I can easily read it) running this manually > gives 351 entries and looks to contain the expected commits. So I'm > confused what's happening? That's difficult to tell without a peek at the repository. Did you compare 'gitk HEAD' to 'gitk HEAD -- WRITING'? I'd expect the latter to be a subset of the former. Note that with a path specified "history simplification" happens, which means that you won't see as many merges as when no path is specified. -- Hannes -- 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
