* Missing next-$date git-tag when pulled-in linux-next.git on top of linus.git @ 2015-01-07 8:24 Sedat Dilek 2015-01-07 10:24 ` Stephen Rothwell 0 siblings, 1 reply; 8+ messages in thread From: Sedat Dilek @ 2015-01-07 8:24 UTC (permalink / raw) To: Stephen Rothwell; +Cc: linux-next, LKML 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 Unfortunately, this is not getting the git-tag "next-20150107" which I fix by... $ git tag next-20150107 Do you happen to know how to do that more elegant? ( I wanted to avoid to run... git pull $git_url --tags ... which gets all -next tags. ) Thanks. - Sedat - ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Missing next-$date git-tag when pulled-in linux-next.git on top of linus.git 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 0 siblings, 1 reply; 8+ messages in thread From: Stephen Rothwell @ 2015-01-07 10:24 UTC (permalink / raw) To: Sedat Dilek; +Cc: linux-next, LKML [-- Attachment #1: Type: text/plain, Size: 746 bytes --] 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. -- Cheers, Stephen Rothwell sfr@canb•auug.org.au [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 819 bytes --] ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Missing next-$date git-tag when pulled-in linux-next.git on top of linus.git 2015-01-07 10:24 ` Stephen Rothwell @ 2015-01-07 13:47 ` Sedat Dilek 2015-01-07 20:52 ` Stephen Rothwell 0 siblings, 1 reply; 8+ messages in thread From: Sedat Dilek @ 2015-01-07 13:47 UTC (permalink / raw) To: Stephen Rothwell; +Cc: linux-next, LKML 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? - Sedat - ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Missing next-$date git-tag when pulled-in linux-next.git on top of linus.git 2015-01-07 13:47 ` Sedat Dilek @ 2015-01-07 20:52 ` Stephen Rothwell 2015-02-03 20:06 ` Sedat Dilek 0 siblings, 1 reply; 8+ messages in thread From: Stephen Rothwell @ 2015-01-07 20:52 UTC (permalink / raw) To: Sedat Dilek; +Cc: linux-next, LKML [-- 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 --] ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Missing next-$date git-tag when pulled-in linux-next.git on top of linus.git 2015-01-07 20:52 ` Stephen Rothwell @ 2015-02-03 20:06 ` Sedat Dilek 2015-02-03 20:20 ` Sedat Dilek 2015-02-03 20:47 ` Stephen Rothwell 0 siblings, 2 replies; 8+ messages in thread From: Sedat Dilek @ 2015-02-03 20:06 UTC (permalink / raw) To: Stephen Rothwell; +Cc: linux-next, LKML On Wed, Jan 7, 2015 at 9:52 PM, Stephen Rothwell <sfr@canb•auug.org.au> wrote: > 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 > 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 - ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Missing next-$date git-tag when pulled-in linux-next.git on top of linus.git 2015-02-03 20:06 ` Sedat Dilek @ 2015-02-03 20:20 ` Sedat Dilek 2015-02-03 20:47 ` Stephen Rothwell 1 sibling, 0 replies; 8+ messages in thread From: Sedat Dilek @ 2015-02-03 20:20 UTC (permalink / raw) To: Stephen Rothwell; +Cc: linux-next, LKML On Tue, Feb 3, 2015 at 9:06 PM, Sedat Dilek <sedat.dilek@gmail•com> wrote: > On Wed, Jan 7, 2015 at 9:52 PM, Stephen Rothwell <sfr@canb•auug.org.au> wrote: >> 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 >> > > 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? > Here I use git v2.2.2. - Sedat - ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Missing next-$date git-tag when pulled-in linux-next.git on top of linus.git 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 1 sibling, 1 reply; 8+ messages in thread From: Stephen Rothwell @ 2015-02-03 20:47 UTC (permalink / raw) To: Sedat Dilek; +Cc: linux-next, LKML [-- Attachment #1: Type: text/plain, Size: 739 bytes --] Hi Sedat, On Tue, 3 Feb 2015 21:06:45 +0100 Sedat Dilek <sedat.dilek@gmail•com> wrote: > > $ 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 sorry about that, try $ git fetch linux-next tag next-20150203 -- Cheers, Stephen Rothwell sfr@canb•auug.org.au [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 819 bytes --] ^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Missing next-$date git-tag when pulled-in linux-next.git on top of linus.git 2015-02-03 20:47 ` Stephen Rothwell @ 2015-02-03 20:59 ` Sedat Dilek 0 siblings, 0 replies; 8+ messages in thread From: Sedat Dilek @ 2015-02-03 20:59 UTC (permalink / raw) To: Stephen Rothwell; +Cc: linux-next, LKML On Tue, Feb 3, 2015 at 9:47 PM, Stephen Rothwell <sfr@canb•auug.org.au> wrote: > Hi Sedat, > > On Tue, 3 Feb 2015 21:06:45 +0100 Sedat Dilek <sedat.dilek@gmail•com> wrote: >> >> $ 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 > > sorry about that, try > > $ git fetch linux-next tag next-20150203 > Thanks, that worked! $ LC_ALL=C git checkout Linux-v3.19-rc7 $ LC_ALL=C git fetch linux-next tag next-20150203 $ LC_ALL=C git checkout -b Linux-next-20150203 next-20150203 - Sedat - ^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2015-02-03 21:00 UTC | newest] Thread overview: 8+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox