Date: Tue, 12 Aug 2008 13:25:17 -0700 (PDT)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Yoshinori Sato <ysato@users.sourceforge.jp>
cc: Sam Ravnborg <sam@ravnborg.org>, Andrew Morton <akpm@linux-foundation.org>,
       linux-kernel@vger.kernel.org
Subject: Re: [PATCH] h8300 move header files
In-Reply-To: <87myjiq960.wl%ysato@users.sourceforge.jp>
Message-ID: <alpine.LFD.1.10.0808121322190.3462@nehalem.linux-foundation.org>
References: <871w0wvgng.wl%ysato@users.sourceforge.jp> <20080811170534.22f26b7e.akpm@linux-foundation.org> <20080812051101.GA21095@uranus.ravnborg.org> <87myjiq960.wl%ysato@users.sourceforge.jp>
User-Agent: Alpine 1.10 (LFD 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1070
Lines: 28


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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/