mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: valdis.kletnieks@vt.edu
To: "Tobin C. Harding" <me@tobin.cc>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Petr Mladek <pmladek@suse.com>, "Theodore Ts'o" <tytso@mit.edu>,
	Arnd Bergmann <arnd@arndb.de>,
	kernelnewbies@kernelnewbies.org, linux-kernel@vger.kernel.org,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH] vsprintf: fix build warning
Date: Mon, 09 Jul 2018 22:28:14 -0400	[thread overview]
Message-ID: <7018.1531189694@turing-police.cc.vt.edu> (raw)
In-Reply-To: <20180709234203.GG4447@eros>

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

On Tue, 10 Jul 2018 09:42:03 +1000, "Tobin C. Harding" said:

> I was under the impression that each maintainer constantly rebased their
> next branches and that was why one has to checkout the tagged linux-next
> each day instead of just pulling.

Close, but no cigar.  The maintainers don't rebase their -next branches, but
due to the way linux-next merges 200+ trees on top of current Linus tree,
*that* ends up rebasing every day.

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

      parent reply	other threads:[~2018-07-10  2:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-06 13:47 Arnd Bergmann
2018-07-06 14:42 ` Sergey Senozhatsky
2018-07-06 15:49   ` Steven Rostedt
2018-07-09  9:45     ` Petr Mladek
2018-07-09 23:15     ` Tobin C. Harding
2018-07-09 23:42     ` Tobin C. Harding
2018-07-10  0:05       ` Sergey Senozhatsky
2018-07-10  2:27       ` Steven Rostedt
2018-07-10  2:28       ` valdis.kletnieks [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=7018.1531189694@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@tobin.cc \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=tytso@mit.edu \
    /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®