From: Sam Ravnborg <sam@ravnborg.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, rth@twiddle.net,
ink@jurassic.park.msu.ru
Subject: Alpha - move header files [Was Re: [PATCH] h8300 move header files]
Date: Fri, 15 Aug 2008 00:01:08 +0200 [thread overview]
Message-ID: <20080814220108.GA10536@uranus.ravnborg.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0808121322190.3462@nehalem.linux-foundation.org>
On Tue, Aug 12, 2008 at 01:25:17PM -0700, 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.
>
I have build-tested alpha with a simple header file move.
Can I ask you to do a simple move of all header files for alpha
like you did for h8300.
[I could set up a git tree etc. but being busy with my new house arm]
Thanks,
Sam
prev parent reply other threads:[~2008-08-14 22:00 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
2008-08-14 22:01 ` Sam Ravnborg [this message]
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=20080814220108.GA10536@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
--cc=torvalds@linux-foundation.org \
--cc=ysato@users.sourceforge.jp \
/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