On 2017-06-05 09:01:33 [+0100], Piotr Gregor wrote: > To setup remote tracking of the branch stable/v1.0 > git checkout with --track option can be used: > git checkout -b stable/v1.0 --track origin/stable/v1.0 > Otherwise when git checkout -b stable/v1.0 is used > branch may not be properly set up to track it's remote counterpart > (given git option) and users may be confused due to no files present > in the folder, but README. > > Signed-off-by: Piotr Gregor <pgregor@xxxxxxxxxxxxxxxxxxxxxx> > --- > README | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/README b/README > index a618eb5..47e3e54 100644 > --- a/README > +++ b/README > @@ -4,3 +4,10 @@ The master branch is unused. You should use an existing branch instead. > > The stable/v1.0 branch contains the old stable version. > The unstable/devel branches contain the development versions. > + > +To checkout stable/v1.0 and setup remote tracking to /origin/stable/v1.0 please do: > + git checkout -b stable/v1.0 origin/stable/v1.0 > +or > + git checkout -b stable/v1.0 --track origin/stable/v1.0 > +and similarly for the unstable/devel/v1.1.1 branch please do: > + git checkout -b unstable/devel/v1.1.1 --track origin/unstable/devel/v1.1.1 That is mostly what I asked for. "Newer" git will accept git checkout stable/v1.0 go for the remote branch and track. But the long version is fine, too. You could maybe add a git branch -r to get an overview of the available remote branches. This is probably helpful for someone not familiar with git. Sebastian -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
