linux-kernel - Re: Missing next-$date git-tag when pulled-in linux-next.git on top of linus.git

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+icZUUL6pT9L8omUuvOfs4biYgOu6sE11n2o7v8F3fVXoLf+w@mail.gmail.com>
Date:	Tue, 3 Feb 2015 21:06:45 +0100
From:	Sedat Dilek <sedat.dilek@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next <linux-next@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Missing next-$date git-tag when pulled-in linux-next.git on top
 of linus.git

On Wed, Jan 7, 2015 at 9:52 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi Sedat,
>
> On Wed, 7 Jan 2015 14:47:53 +0100 Sedat Dilek <sedat.dilek@...il.com> wrote:
>>
>> On Wed, Jan 7, 2015 at 11:24 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>> > Hi Sedat,
>> >
>> > On Wed, 7 Jan 2015 09:24:57 +0100 Sedat Dilek <sedat.dilek@...il.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
>

Sorry for the late response, I wanted to test today's next-20150203...

My base is always linux.git...

$ cd linux/

$ git checkout -b Linux-v3.19-rc7 v3.19-rc7

$ git checkout Linux-v3.19-rc7
Zu Branch 'Linux-v3.19-rc7' gewechselt

$ git fetch linux-next next-20150203
remote: Counting objects: 62716, done.
remote: Compressing objects: 100% (14620/14620), done.
remote: Total 62716 (delta 53326), reused 57198 (delta 47960)
Empfange Objekte: 100% (62716/62716), 12.84 MiB | 217.00 KiB/s, Fertig.
Löse Unterschiede auf: 100% (53326/53326), abgeschlossen mit 7064
lokalen Objekten.
Von git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next
 * tag                         next-20150203 -> FETCH_HEAD

$ LC_ALL=C git checkout -b Linux-next-20150203 next-20150203
fatal: Cannot update paths and switch to branch 'Linux-next-20150203'
at the same time.
Did you intend to checkout 'next-20150203' which can not be resolved as commit?

$ LC_ALL=C git checkout -b Linux-next-20150203 tags/next-20150203
fatal: Cannot update paths and switch to branch 'Linux-next-20150203'
at the same time.
Did you intend to checkout 'tags/next-20150203' which can not be
resolved as commit?

- Sedat -
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/