mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux Watchdog Mailing List <linux-watchdog@vger.kernel.org>
Subject: Re: [GIT PULL REQUEST] watchdog - v3.11-rc1
Date: Fri, 12 Jul 2013 16:22:41 +1000	[thread overview]
Message-ID: <20130712162241.08c8dd775abd0d6792b4927b@canb.auug.org.au> (raw)
In-Reply-To: <20130711203424.GE14258@spo001.leaseweb.com>

[-- Attachment #1: Type: text/plain, Size: 844 bytes --]

Hi Wim,

On Thu, 11 Jul 2013 22:34:24 +0200 Wim Van Sebroeck <wim@iguana.be> wrote:
>
> Please pull from 'master' branch of
> 	git://www.linux-watchdog.org/linux-watchdog.git

This was all rebased in the last day from what has been in linux-next for
some time.  All the patches are the same, so the rebase achieved nothing
positive at all.  Please don't do this (see I am still much nicer than
Linus :-)).  Just submit what you have in linux-next which has already
been tested (presumably) and Linus can fix up any conflicts (in this case
there were nothing significant anyway).

Also, you might like to consider using "git request-pull" to generate a
starting place for your pull request rather than sending all the commit
messages and the diff in line.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-07-12  6:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11 20:34 Wim Van Sebroeck
2013-07-12  6:22 ` Stephen Rothwell [this message]
2013-07-13 12:07   ` Wim Van Sebroeck

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=20130712162241.08c8dd775abd0d6792b4927b@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=wim@iguana.be \
    /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®