From: "Stephen P. Smith" <ischis2@cox.net>
To: Git List <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>, "Stephen P. Smith" <ischis2@cox.net>
Subject: [PATCH V2] user-manual: remove temporary branch entry from todo list
Date: Mon, 28 Dec 2015 13:16:44 -0700 [thread overview]
Message-ID: <1451333804-6431-1-git-send-email-ischis2@cox.net> (raw)
In-Reply-To: <xmqqr3i6lbx2.fsf@gitster.mtv.corp.google.com>
In the section on "How to check out a differnet version of a project"
the "new" branch is used as a temporary branch.
A detached HEAD was not used since it was a new feature introduced
just a couple weeks prior.
The section could be changed to use and explain a detached HEAD,
except that would increase the learning curve early in the manual.
Detached HEADs are discussed a couple sections later under
"Examining an old version without creating a new branch".
Signed-off-by: Stephen P. Smith <ischis2@cox.net>
---
Documentation/user-manual.txt | 3 ---
1 file changed, 3 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index 1c790ac..18e2f1e 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -4636,9 +4636,6 @@ Scan email archives for other stuff left out
Scan man pages to see if any assume more background than this manual
provides.
-Simplify beginning by suggesting disconnected head instead of
-temporary branch creation?
-
Add more good examples. Entire sections of just cookbook examples
might be a good idea; maybe make an "advanced examples" section a
standard end-of-chapter section?
--
2.7.0-rc2
next prev parent reply other threads:[~2015-12-28 20:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 0:47 [PATCH] user-manual: remove temporary branch entry from todo list Stephen P. Smith
2015-12-28 2:41 ` Junio C Hamano
2015-12-28 6:02 ` Stephen & Linda Smith
2015-12-28 17:29 ` Junio C Hamano
2015-12-28 20:16 ` Stephen P. Smith [this message]
2015-12-28 18:41 ` Stephen & Linda Smith
2015-12-28 21:44 ` Junio C Hamano
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=1451333804-6431-1-git-send-email-ischis2@cox.net \
--to=ischis2@cox.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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;
as well as URLs for NNTP newsgroup(s).