From: John Kacur <jkacur@redhat.com>
To: rolf.freitag@email.de
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Where are the branches for stable/v1.0 and unstable/devel?
Date: Wed, 31 May 2017 16:48:16 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.20.1705311645190.6177@riemann> (raw)
In-Reply-To: <trinity-363cee20-7cf0-4d43-b5d7-058ae3582716-1495921425917@3capp-webde-bs06>
[-- Attachment #1: Type: text/plain, Size: 2616 bytes --]
On Sat, 27 May 2017, rolf.freitag@email.de wrote:
> Hi Vedang,
>
> On Mon, 2017-05-22 at 20:43 +0200, vedang.patel@intel.com wrote:
> > ...
> > The following 2 branches in the above repository have been most
> > recently updated and correspond to the stable and unstable branch:
> > 0e6c2ca28adbaeb668ca35210cec546f89938bfa refs/heads/stable/devel
> > /v1.0.1
> > 44de1a494583c33e72335221360085f9e1faad2b refs/heads/unstable/dev
> > el/v1.1.1
> > There is also a stable/v1.0 branch:
> > d48504b8e85961afab1cb0bd346624eb31527197 refs/heads/stable/v1.0
> >
> > the wiki page you mentioned in your email is outdated. Please refer to
> > https://wiki.linuxfoundation.org/realtime/documentation/howto/tools/cyc[https://wiki.linuxfoundation.org/realtime/documentation/howto/tools/cyc]
> > lictest for the latest info.
>
> Ok, due to https://wiki.linuxfoundation.org/realtime/documentation/howto/tools/rt-tests
> i can get the stable/v1.0 via:
>
> # git clone git://git.kernel.org/pub/scm/utils/rt-tests/rt-tests.git
> # cd rt-tests
> # git checkout stable/v1.0
>
> But when i try it with the other two versions,
>
> git checkout stable/devel
> git checkout unstable/dev
>
> i get no checkout and an error:
>
> error: pathspec 'stable' did not match any file(s) known to git.
>
> Regards,
>
> Rolf
Here is how (one way) to check out the stable and the unstable
branches.
git clone git://git.kernel.org/pub/scm/utils/rt-tests/rt-tests.git
Cloning into 'rt-tests'...
remote: Counting objects: 2914, done.
remote: Total 2914 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (2914/2914), 554.11 KiB | 513.00 KiB/s, done.
Resolving deltas: 100% (1760/1760), done.
Checking connectivity... done.
[jkacur@riemann tmp]$ cd rt-tests/
[jkacur@riemann rt-tests]$ git branch -a
* master
remotes/origin/HEAD -> origin/master
remotes/origin/devel/v0.96
remotes/origin/devel/v0.96-spikes
remotes/origin/devel/v0.97
remotes/origin/devel/v0.98
remotes/origin/master
remotes/origin/stable/devel/v1.0.1
remotes/origin/stable/v1.0
remotes/origin/unstable/devel/v1.1.1
remotes/origin/v0.93-devel
remotes/origin/v0.94-devel
[jkacur@riemann rt-tests]$ git checkout -b stable/v1.0 origin/stable/v1.0
Branch stable/v1.0 set up to track remote branch stable/v1.0 from origin.
Switched to a new branch 'stable/v1.0'
[jkacur@riemann rt-tests]$ git checkout -b unstable/devel/v1.1.1
origin/unstable/devel/v1.1.1
Branch unstable/devel/v1.1.1 set up to track remote branch
unstable/devel/v1.1.1 from origin.
Switched to a new branch 'unstable/devel/v1.1.1'
next prev parent reply other threads:[~2017-05-31 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 18:43 Where are the branches for stable/v1.0 and unstable/devel? rolf.freitag
2017-05-22 20:01 ` Patel, Vedang
2017-05-22 23:14 ` Aw: " rolf.freitag
2017-05-27 21:43 ` rolf.freitag
2017-05-31 14:48 ` John Kacur [this message]
2017-06-02 8:42 ` Sebastian Andrzej Siewior
2017-06-05 7:09 ` Piotr Gregor
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=alpine.LFD.2.20.1705311645190.6177@riemann \
--to=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=rolf.freitag@email.de \
/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