mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: Someone Something <fordhaivat@gmail.com>,
	greg@kroah.com, linux-kernel@vger.kernel.org, joe@perches.com,
	akpm@linux-foundation.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] Fixes a small error in Documentation/HOWTO
Date: Mon, 4 Apr 2011 11:18:29 -0700	[thread overview]
Message-ID: <20110404111829.af8bc108.rdunlap@xenotime.net> (raw)
In-Reply-To: <4D99230C.6040403@cn.fujitsu.com>

On Mon, 04 Apr 2011 09:46:52 +0800 Li Zefan wrote:

> > Your updated link for HOWTO is just for linux-2.6.38. This link
> > should be up-to-date kernel code. So i have corrected your
> > patch like following.
> > 
> > Thanks.
> > Best Regards.
> > Harry Wei.
> > 
> > Signed-off-by: Someone Something <fordhaivat@gmail.com>
> > Signed-off-by: Harry Wei <harryxiyou@gmail.com>
> 
> Did he sign the patch? If not, you can't do this, and Instead you
> must ask him for his SOB.
> 
> And I'll appreciate if you add:
> 
> 	From: Someone ...
> 
> because your change is not significant enough to make you the author
> of the patch.

Regardless of that latter part, we cannot merge the patch from SS,
like Xiaochen Wang said, since the name is false.


> > ---
> >  Documentation/HOWTO |    2 +-
> >  1 files changed, 1 insertions(+), 1 deletions(-)
> > 
> > diff --git a/Documentation/HOWTO b/Documentation/HOWTO
> > index 365bda9..81bc1a9 100644
> > --- a/Documentation/HOWTO
> > +++ b/Documentation/HOWTO
> > @@ -209,7 +209,7 @@ tools.  One such tool that is particularly recommended is the Linux
> >  Cross-Reference project, which is able to present source code in a
> >  self-referential, indexed webpage format. An excellent up-to-date
> >  repository of the kernel code may be found at:
> > -	http://users.sosdg.org/~qiyong/lxr/
> > +	http://lxr.linux.no/+trees
> >  
> >  
> >  The development process


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  reply	other threads:[~2011-04-04 18:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-02 20:03 Someone Something
2011-04-02 23:48 ` Someone Something
2011-04-03  4:52 ` Harry Wei
2011-04-03  6:32   ` Xiaochen Wang
2011-04-04  1:46   ` Li Zefan
2011-04-04 18:18     ` Randy Dunlap [this message]
     [not found]       ` <BANLkTinSC1UTEQxS0iCKu4tMX-9CUY3rJg@mail.gmail.com>
2011-04-05  2:07         ` Harry Wei
2011-05-05 22:07           ` Randy Dunlap
2011-05-05 23:55             ` Harry Wei
2011-05-06 21:43               ` Randy Dunlap

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=20110404111829.af8bc108.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=akpm@linux-foundation.org \
    --cc=fordhaivat@gmail.com \
    --cc=greg@kroah.com \
    --cc=joe@perches.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    /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

all inboxes | Powered by JetHome®