git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Karl Hasselström" <kha@treskal.com>
Cc: git@vger.kernel.org
Subject: Re: bisect / history preserving on rename + update
Date: Tue, 14 Aug 2007 16:19:43 +0200	[thread overview]
Message-ID: <1187101183.12828.191.camel@chaos> (raw)
In-Reply-To: <20070814111828.GA15399@diana.vm.bytemark.co.uk>

On Tue, 2007-08-14 at 13:18 +0200, Karl Hasselström wrote:
> On 2007-08-14 13:06:59 +0200, Thomas Gleixner wrote:
> 
> > On Tue, 2007-08-14 at 12:50 +0200, Karl Hasselström wrote:
> >
> > > 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.
> 
> Have you tried running blame with -C, or -C -C? That will make it try
> harder to identify lines originating from other files.

Does not help. Strange enough it results in

# git blame include/B

b4062b16 include/A (Joe Hacker      2007-08-14 10:52:28 +0200  1) #ifndef _A_H_
b4062b16 include/A (Joe Hacker      2007-08-14 10:52:28 +0200  2) #define _A_H_
b4062b16 include/A (Joe Hacker      2007-08-14 10:52:28 +0200  3) 
b4062b16 include/A (Joe Hacker      2007-08-14 10:52:28 +0200  4) #define TEST_1 1
f098c4ad include/B (Thomas Gleixner 2007-08-14 16:01:05 +0200  5) #define TEST_2 2
f098c4ad include/B (Thomas Gleixner 2007-08-14 16:01:05 +0200  6) 
f098c4ad include/B (Thomas Gleixner 2007-08-14 16:01:05 +0200  7) #endif

	tglx

  reply	other threads:[~2007-08-14 14:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-14  8:38 bisect / history preserving on rename + update Thomas Gleixner
2007-08-14  9:33 ` Karl Hasselström
2007-08-14 10:16   ` Thomas Gleixner
2007-08-14 10:50     ` Karl Hasselström
2007-08-14 11:06       ` Thomas Gleixner
2007-08-14 11:12         ` David Kastrup
2007-08-14 11:18         ` Karl Hasselström
2007-08-14 14:19           ` Thomas Gleixner [this message]
2007-08-14 14:45             ` David Kastrup
2007-08-14 10:03 ` David Kastrup
2007-08-14 16:14 ` Linus Torvalds
2007-08-25  4:59   ` Junio C Hamano
2007-08-25  7:35     ` David Kastrup
2007-08-25 15:38     ` Linus Torvalds
2007-08-25 17:23       ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1187101183.12828.191.camel@chaos \
    --to=tglx@linutronix.de \
    --cc=git@vger.kernel.org \
    --cc=kha@treskal.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).