All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	Laxman Dewangan <ldewangan@nvidia.com>
Subject: Re: [GIT PULL] GPIO bulk changes for kernel v4.6
Date: Fri, 18 Mar 2016 10:01:49 +0100	[thread overview]
Message-ID: <CACRpkdawWP42O+dy2eJOQXr+aJqpQyRVWLFN5s66EA3wsTEz8A@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFwV4Cq=4zJc6Fw0yAGrTmci_DFAjJKxkk05pjJJf3iYbA@mail.gmail.com>

On Fri, Mar 18, 2016 at 7:07 AM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> On Thu, Mar 17, 2016 at 1:59 AM, Linus Walleij <linus.walleij@linaro.org> wrote:
>>
>> The end result should be clean but the history is a bit messy.
>
> Gaah. I took the tree, but I didn't realize just *how* messy it was. I
> doubt you did either.

Certainly not. I wasn't even aware that things could be screwed up so
much and still look OK on the surface. I'll certainly be more cautious
about pulling branches in the future.

Yours,
Linus Walleij

  parent reply	other threads:[~2016-03-18  9:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-17  8:59 [GIT PULL] GPIO bulk changes for kernel v4.6 Linus Walleij
2016-03-18  6:07 ` Linus Torvalds
2016-03-18  6:07   ` Laxman Dewangan
2016-03-18  7:15     ` Linus Torvalds
2016-03-18 14:32       ` Johannes Schindelin
2016-03-18 15:43         ` Junio C Hamano
2016-03-18 15:43           ` Junio C Hamano
2016-03-18 15:47         ` Linus Torvalds
2016-03-18 16:37           ` Junio C Hamano
2016-03-18 16:37             ` Junio C Hamano
2016-03-18 17:01             ` Linus Torvalds
2016-03-18 17:16               ` Junio C Hamano
2016-03-18 17:16                 ` Junio C Hamano
2016-03-18  9:01   ` Linus Walleij [this message]
2016-03-18  9:39     ` Laxman Dewangan
2016-03-18 15:56       ` Linus Torvalds

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=CACRpkdawWP42O+dy2eJOQXr+aJqpQyRVWLFN5s66EA3wsTEz8A@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=ldewangan@nvidia.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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.