From: Ralf Mardorf <ralf.mardorf@alice-dsl.net>
To: linux-rt-users@vger.kernel.org
Subject: Re: [ANNOUNCE] v4.14.12-rt10
Date: Tue, 16 Jan 2018 08:16:14 +0100 [thread overview]
Message-ID: <20180116081614.106781c2@archlinux.localdomain> (raw)
In-Reply-To: <201801152227.58933.gheskett@shentel.net>
On Mon, 15 Jan 2018 22:27:58 -0500, Gene Heskett wrote:
>rock64@rock64:/media/slash/home/rock64/Downloads$
>git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git
>v4.14.12-rt10
>
>-bash:
>git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git:
>No such file or directory
>
>The git installed is: 2.11.0 if thats a clue.
Hi,
I'm not an advanced git user, but shouldn't you use a command instead of just an URL?
[rocketmouse@archlinux .tmp]$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-rt-devel.git
Cloning into 'linux-rt-devel'...
remote: Counting objects: 6197952, done.
remote: Compressing objects: 100% (944316/944316), done.
remote: Total 6197952 (delta 5210675), reused 6196073 (delta 5209729)
Receiving objects: 100% (6197952/6197952), 1.11 GiB | 708.00 KiB/s, done.
Resolving deltas: 100% (5210675/5210675), done.
[rocketmouse@archlinux .tmp]$
[rocketmouse@archlinux .tmp]$
[rocketmouse@archlinux .tmp]$
[rocketmouse@archlinux .tmp]$
[rocketmouse@archlinux .tmp]$ cd linux-rt-devel/
[rocketmouse@archlinux linux-rt-devel]$
[rocketmouse@archlinux linux-rt-devel]$
[rocketmouse@archlinux linux-rt-devel]$
[rocketmouse@archlinux linux-rt-devel]$
[rocketmouse@archlinux linux-rt-devel]$ git branch
* master
[rocketmouse@archlinux linux-rt-devel]$ git describe --tags $(git rev-list --tags --max-count=10)
v4.14.12-rt10-patches
v4.14.12-rt10
v4.14.12-405-g5536f5491a2e
v4.14.12-rt10-rebase
v4.14.12-380-g038ecb81aa81
v4.14.12-379-gca6de2d16341
v4.14.12-378-g278da228d04c
v4.14.12-377-g85db952da1f4
v4.14.12-376-g0cc094ba4d14
v4.14.12-375-g54a259a815f7
[rocketmouse@archlinux linux-rt-devel]$ git checkout v4.14.12-rt10
Note: checking out 'v4.14.12-rt10'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b <new-branch-name>
HEAD is now at df269158d3f0... v4.14.12-rt10
[rocketmouse@archlinux linux-rt-devel]$ git branch
* (HEAD detached at v4.14.12-rt10)
master
[rocketmouse@archlinux linux-rt-devel]$ git checkout master
Previous HEAD position was df269158d3f0... v4.14.12-rt10
Switched to branch 'master'
Your branch is up to date with 'origin/master'.
[rocketmouse@archlinux linux-rt-devel]$ git describe
v4.14
[rocketmouse@archlinux linux-rt-devel]$ git remote update
Fetching origin
[rocketmouse@archlinux linux-rt-devel]$ git pull --all
Fetching origin
Already up to date.
Regards,
Ralf
next prev parent reply other threads:[~2018-01-16 7:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 12:34 [ANNOUNCE] v4.14.12-rt10 Sebastian Andrzej Siewior
2018-01-09 14:29 ` Gene Heskett
2018-01-12 18:42 ` Sebastian Andrzej Siewior
2018-01-12 22:41 ` Gene Heskett
2018-01-13 5:07 ` Ralf Mardorf
2018-01-16 3:27 ` Gene Heskett
2018-01-16 7:16 ` Ralf Mardorf [this message]
2018-01-16 12:35 ` Gene Heskett
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=20180116081614.106781c2@archlinux.localdomain \
--to=ralf.mardorf@alice-dsl.net \
--cc=linux-rt-users@vger.kernel.org \
/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