linux-kernel - Re: git mv (was Re: [git pull] ACPI & Suspend patches for 2.6.29-rc0)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 9 Jan 2009 22:27:57 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Len Brown <lenb@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-acpi@...r.kernel.org,
	Linux Power Management List <linux-pm@...ts.osdl.org>
Subject: Re: git mv (was Re: [git pull] ACPI & Suspend patches for 2.6.29-rc0)

> 
> So yeah, "--follow" is broken. It's really a quick hack there for people 
> who come from some other SCM to feel more comfy with git. If you come from 
> SVN or CVS, you never had proper history, and you never had "gitk" anyway, 
> and so "gitk --follow" doesn't really work. But it makes the pure 
> _textual_ logs look a bit like CVS/SVN.
> 
> I'd love to make --follow work better and integrate more, but I've been so 
> successful at never using it myself that I don't much care. And it really 
> is not a very natural thing for git to do, so the hackiness is somewhat 
> inherent.

What other ways exist so I can see what the heck davem did to
arch/sparc64/kernel/irq.c then?

I know he added IRQ stacks - but how did the patch look like?
I know no other way to find the old history than to do:

    git log --follow arch/sparc/kernel/irq_64.c

But this also give me what I want. I'm just curious if there is
a better way - in the case where you know the old name.


	Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/