On Mon, Jul 4, 2016 at 1:39 PM, Konstantin Khomoutov
<[email protected]> wrote:
> On Mon, 4 Jul 2016 12:45:39 -0400
> shawn wilson <[email protected]> wrote:
>
>
> To achieve what you're after I used `git subtree split` followed by
> `git filter-branch --tree-filter ...` which moved all the files under
> the directory hierarchy `git subtree split` removes.
>
Ah, that looks like it should work - thanks
> I know Git tracks content, not files (and directory) but still many
> folks have "stable" directories for their files, assign certain
> semantics to them etc. I've needed such transfers myself, and this
> topic has been raised more than once by folks over there on the
> git-users mailing list.
Or just an option for git {rm,mv,cp} that would allow simple rewriting
of history. Ie:
git mv HEAD~3.. -- foo bar
(obviously not the sanest thing in most cases but would be a shorter
reach than filter-branch - and if newest isn't head then it'd what?
move it back during commits for who knows what - still...)
Thanks for pointing out the users list - didn't notice it and sorry
for posting a user question on a dev list.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html