public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Nick Terrell <nickrterrell@gmail•com>
Cc: linux-next@vger•kernel.org, linux-crypto@vger•kernel.org,
	linux-btrfs@vger•kernel.org,
	squashfs-devel@lists•sourceforge.net,
	linux-f2fs-devel@lists•sourceforge.net,
	linux-kernel@vger•kernel.org, "Kernel Team" <Kernel-team@fb•com>,
	"Nick Terrell" <terrelln@fb•com>, "Chris Mason" <clm@fb•com>,
	"Petr Malat" <oss@malat•biz>, "Yann Collet" <cyan@fb•com>,
	"Christoph Hellwig" <hch@infradead•org>,
	"Michał Mirosław" <mirq-linux@rere•qmqm.pl>,
	"David Sterba" <dsterba@suse•cz>,
	"Oleksandr Natalenko" <oleksandr@natalenko•name>,
	"Felix Handte" <felixh@fb•com>,
	"Eric Biggers" <ebiggers@kernel•org>,
	"Randy Dunlap" <rdunlap@infradead•org>,
	"Paul Jones" <paul@pauljones•id.au>,
	"Tom Seewald" <tseewald@gmail•com>
Subject: Re: [GIT PULL][v12] zstd changes for linux-next
Date: Tue, 5 Oct 2021 13:26:59 +1100	[thread overview]
Message-ID: <20211005132659.6774f10b@canb.auug.org.au> (raw)
In-Reply-To: <20211005014118.3164585-1-nickrterrell@gmail.com>

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

Hi Nick,

On Mon,  4 Oct 2021 18:41:18 -0700 Nick Terrell <nickrterrell@gmail•com> wrote:
>
> From: Nick Terrell <terrelln@fb•com>
> 
> The following changes since commit a25006a77348ba06c7bc96520d331cd9dd370715:
> 
>   Add linux-next specific files for 20211001 (2021-10-01 17:07:37 +1000)
> 
> are available in the Git repository at:
> 
>   git@github•com:terrelln/linux.git tags/v12-zstd-1.4.10
> 
> for you to fetch changes up to 5210ca33b09bed5e09f72e9b46a3220f64597f8c:
> 
>   MAINTAINERS: Add maintainer entry for zstd (2021-10-04 18:14:42 -0700)
> 
> I would like to merge this pull request into linux-next to bake, and then submit
> the PR to Linux in the 5.16 merge window. If you have been a part of the
> discussion, are a maintainer of a caller of zstd, tested this code, or otherwise
> been involved, thank you! And could you please respond below with an appropiate
> tag, so I can collect support for the PR

Sorry, but you can't base a branch on linux-next itself (since
linux-next - and many of the trees it merges - rebases every day).  If
you want a branch included in linux-next, it needs to be based on some
stable tree/branch, almost always Linus Torvald's tree.

Also, what I need is a branch that I can fetch every day (so its name
must not change) and all you do is update that branch to any newer
version if/when you are satisfied that it is ready for merging.

Also, I would like a git URL that does not require a github account ...
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2021-10-05  2:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05  1:41 [GIT PULL][v12] zstd changes for linux-next Nick Terrell
2021-10-05  2:26 ` Stephen Rothwell [this message]
2021-10-05  3:10   ` Nick Terrell
2021-10-06  7:26 ` Paul Jones
2021-10-06  7:33 ` Oleksandr Natalenko

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=20211005132659.6774f10b@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=Kernel-team@fb$(echo .)com \
    --cc=clm@fb$(echo .)com \
    --cc=cyan@fb$(echo .)com \
    --cc=dsterba@suse$(echo .)cz \
    --cc=ebiggers@kernel$(echo .)org \
    --cc=felixh@fb$(echo .)com \
    --cc=hch@infradead$(echo .)org \
    --cc=linux-btrfs@vger$(echo .)kernel.org \
    --cc=linux-crypto@vger$(echo .)kernel.org \
    --cc=linux-f2fs-devel@lists$(echo .)sourceforge.net \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mirq-linux@rere$(echo .)qmqm.pl \
    --cc=nickrterrell@gmail$(echo .)com \
    --cc=oleksandr@natalenko$(echo .)name \
    --cc=oss@malat$(echo .)biz \
    --cc=paul@pauljones$(echo .)id.au \
    --cc=rdunlap@infradead$(echo .)org \
    --cc=squashfs-devel@lists$(echo .)sourceforge.net \
    --cc=terrelln@fb$(echo .)com \
    --cc=tseewald@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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