linux-kernel - Re: [PATCH] h8300 move header files

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]

Message-ID: <alpine.LFD.1.10.0808121322190.3462@nehalem.linux-foundation.org>
Date:	Tue, 12 Aug 2008 13:25:17 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Yoshinori Sato <ysato@...rs.sourceforge.jp>
cc:	Sam Ravnborg <sam@...nborg.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] h8300 move header files



On Tue, 12 Aug 2008, Yoshinori Sato wrote:
> 
> My h8300 repository can't public access.
> Also difficult pull request.

The nice thing about git is that it doesn't care one whit how something 
gets moved. So you can

 - just send me a regular patch (as a git user, it can be the "git 
   shorthand" kind of patch that has explicit renames, but it can be a 
   traditional patch with delete/create pairs too, and git won't care AT 
   ALL because the end result is the same)

 - or just send me a shell script to do the renames along with a small 
   patch to fix up any other issues that happen as a result of the rename, 
   and a explanation for me to use as a commit message.

Renames in git do not have to be handled as "git" events, unlike many 
other broken models. Git will do the right thing regardless.

			Linus
--
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/