All of lore.kernel.org
 help / color / mirror / Atom feed
From: Piotr Gregor <piotrgregor@rsyncme.org>
To: jkacur@redhat.com
Cc: rolf.freitag@email.de, linux-rt-users@vger.kernel.org
Subject: [PATCH] README: Added info about setting branch --tracking
Date: Mon, 5 Jun 2017 09:01:33 +0100	[thread overview]
Message-ID: <20170605080130.strwcmn6lqptqf76@debian1.home> (raw)

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@quadrant-systems.co.uk>
---
 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
-- 
2.1.4


             reply	other threads:[~2017-06-05  8:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-05  8:01 Piotr Gregor [this message]
2017-06-08  7:57 ` [PATCH] README: Added info about setting branch --tracking Sebastian Andrzej Siewior
2017-06-08 10:19 Piotr Gregor
2017-06-08 12:17 ` Sebastian Andrzej Siewior
2017-06-08 14:16 ` John Kacur

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=20170605080130.strwcmn6lqptqf76@debian1.home \
    --to=piotrgregor@rsyncme.org \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.