From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Sedat Dilek <sedat.dilek@gmail•com>
Cc: linux-next <linux-next@vger•kernel.org>,
LKML <linux-kernel@vger•kernel.org>
Subject: Re: Missing next-$date git-tag when pulled-in linux-next.git on top of linus.git
Date: Thu, 8 Jan 2015 07:52:01 +1100 [thread overview]
Message-ID: <20150108075201.042f9126@canb.auug.org.au> (raw)
In-Reply-To: <CA+icZUVYu2uaAG-sSf5pf_rzGU+BSBAwu9mhBDrCXZ0a2nw1sA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]
Hi Sedat,
On Wed, 7 Jan 2015 14:47:53 +0100 Sedat Dilek <sedat.dilek@gmail•com> wrote:
>
> On Wed, Jan 7, 2015 at 11:24 AM, Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> > Hi Sedat,
> >
> > On Wed, 7 Jan 2015 09:24:57 +0100 Sedat Dilek <sedat.dilek@gmail•com> wrote:
> >>
> >> My workflow looks like this
> >>
> >> # Get mainline Git tree
> >> $ git clone $LINUS_GIT_URL
> >>
> >> # Checkout latest mainline (rc) tag (aka -next's "origin" commit-id)
> >> $ git checkout -b Linux-v3.19-rc3 v3.19-rc3
> >>
> >> # Base to pull in current -next
> >> $ git checkout -b Linux-next-20150107
> >>
> >> # Pull in stuff from next-20150107
> >> $ git pull git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> >> tags/next-20150107
> >
> > Just do
> >
> > $ git pull git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> >
> > That should also fetch the next- tag.
>
> For current -next this is OK.
> Sometimes I needed to test against a specific next-version.
> Any idea?
$ git clone <Linus' tree> next
$ cd next
$ git fetch <Next URL> next-xxxxxxxx
$ git checkout -b Linux-next-xxxxxxxx next-xxxxxxxx
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-01-07 20:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 8:24 Missing next-$date git-tag when pulled-in linux-next.git on top of linus.git Sedat Dilek
2015-01-07 10:24 ` Stephen Rothwell
2015-01-07 13:47 ` Sedat Dilek
2015-01-07 20:52 ` Stephen Rothwell [this message]
2015-02-03 20:06 ` Sedat Dilek
2015-02-03 20:20 ` Sedat Dilek
2015-02-03 20:47 ` Stephen Rothwell
2015-02-03 20:59 ` Sedat Dilek
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=20150108075201.042f9126@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sedat.dilek@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