All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] h8300 move header files
Date: Wed, 13 Aug 2008 16:41:12 -0400	[thread overview]
Message-ID: <87k5ektzpz.wl%ysato@users.sourceforge.jp> (raw)
In-Reply-To: <alpine.LFD.1.10.0808121322190.3462@nehalem.linux-foundation.org>

At Tue, 12 Aug 2008 13:25:17 -0700 (PDT),
Linus Torvalds wrote:
> 
> 
> 
> 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

OK.
please run this script at toplevel.

-- cut here --
#!/bin/sh
mkdir -p arch/h8300/include/asm
git mv include/asm-h8300/* arch/h8300/include/asm
git commit -m 'move include/asm-h8300 to arch/h8300/include/asm'
-- cut here --

And commit log is
Created commit 2f163b8: move include/asm-h8300 to arch/h8300/include/asm
 99 files changed, 0 insertions(+), 0 deletions(-)
 rename {include/asm-h8300 => arch/h8300/include/asm}/Kbuild (100%)
(snip)
 rename {include/asm-h8300 => arch/h8300/include/asm}/virtconvert.h (100%)

All files rename only.

-- 
Yoshinori Sato
<ysato@users.sourceforge.jp>

  reply	other threads:[~2008-08-13 20:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-10 19:01 [PATCH] h8300 move header files Yoshinori Sato
2008-08-12  0:05 ` Andrew Morton
2008-08-12  5:11   ` Sam Ravnborg
2008-08-12 20:18     ` Yoshinori Sato
2008-08-12 20:25       ` Linus Torvalds
2008-08-13 20:41         ` Yoshinori Sato [this message]
2008-08-14 22:01         ` Alpha - move header files [Was Re: [PATCH] h8300 move header files] Sam Ravnborg

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=87k5ektzpz.wl%ysato@users.sourceforge.jp \
    --to=ysato@users.sourceforge.jp \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=torvalds@linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.