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

Re: bisect / history preserving on rename + update

From
TGThomas Gleixner <tglx@linutronix.de>
Date
Aug 14, 2007, 11:06 UTC
Message-ID
<1187089619.12828.183.camel@chaos>
In-Reply-To
<20070814105056.GA14536@diana.vm.bytemark.co.uk>
On Tue, 2007-08-14 at 12:50 +0200, Karl Hasselström wrote:
Show 21 quoted lines
> > 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
Previous: Karl HasselströmNext: David Kastrup
Message 5 of 15 in “bisect / history preserving on rename + update”
  1. Thomas GleixnerAug 14, 2007
  2. Karl HasselströmAug 14, 2007
  3. Thomas GleixnerAug 14, 2007
  4. Karl HasselströmAug 14, 2007
  5. Thomas GleixnerAug 14, 2007
  6. David KastrupAug 14, 2007
  7. Karl HasselströmAug 14, 2007
  8. Thomas GleixnerAug 14, 2007
  9. David KastrupAug 14, 2007
  10. David KastrupAug 14, 2007
  11. Linus TorvaldsAug 14, 2007
  12. Junio C HamanoAug 25, 2007
  13. David KastrupAug 25, 2007
  14. Linus TorvaldsAug 25, 2007
  15. Junio C HamanoAug 25, 2007

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.