On Tue, 2007-08-14 at 12:50 +0200, Karl Hasselström wrote: > > Err. > > > > git-mv A B > > git commit > > edit B > > git commit > > git blame B <- shows the full history of A & B > > > > IMHO that's why we have git-mv > > Try replacing > > $ git-mv A B > > with > > $ mv A B > $ git rm A > $ git add B > > The result is exactly the same. git-mv is just a convenience. Fair enough, but it still does not solve my initial problem of keeping the history of B (former A) intact, while creating a new A which is necessary to compile the tree, simply because I can not change #include <A> to #include <B> for various reasons. tglx - 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
