From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Sam Ravnborg <sam@ravnborg.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] h8300 move header files
Date: Tue, 12 Aug 2008 16:18:31 -0400 [thread overview]
Message-ID: <87myjiq960.wl%ysato@users.sourceforge.jp> (raw)
In-Reply-To: <20080812051101.GA21095@uranus.ravnborg.org>
At Tue, 12 Aug 2008 07:11:01 +0200,
Sam Ravnborg wrote:
>
> >
> > This patch will cause me some pain, because people will occasionally
> > change those headers and the plain-old-patch will break.
> >
> > Some better options are
> >
> > a) merge it into Sam's git tree, then he merges it into 2.6.28-rc1
> >
> > b) you resend the pull request into Linus during the 2.6.28-rc1 merge window
> >
> > c) merge it into mainline immediately
> >
> > Sam, any suggestions here?
>
> c) is preferred so we get this done for as soon as possible.
> And this is a pure file move so it is simple.
Yes. simply move only.
> If you do not have a git tree then just ask Linus to move the header
> files.
>
> Sam
My h8300 repository can't public access.
Also difficult pull request.
--
Yoshinori Sato
<ysato@users.sourceforge.jp>
next prev parent reply other threads:[~2008-08-12 20:19 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 [this message]
2008-08-12 20:25 ` Linus Torvalds
2008-08-13 20:41 ` Yoshinori Sato
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=87myjiq960.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.