From: Stephen & Linda Smith <ischis2@cox.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH] user-manual: remove temporary branch entry from todo list
Date: Sun, 27 Dec 2015 23:02:31 -0700 [thread overview]
Message-ID: <3065044.ki4VpYSZvR@thunderbird> (raw)
In-Reply-To: 1450918023-30309-1-git-send-email-ischis2@cox.net
On Sunday, December 27, 2015 06:41:09 PM Junio C Hamano wrote:
> "Stephen P. Smith" <ischis2@cox.net> writes:
>
> > Remove the suggestion for using a detached HEAD instead of a
> > temporary branch.
>
> That is something we can read from the patch text. Please explain
> why it is a good idea to remove it.
>
> I can think of two completely different reasons:
>
> (1) Maybe the task was done some time ago, and we are seeing a
> stale todo item?
>
> (2) The task the todo item hints at was not done, but maybe it is
> not a good thing to do after all?
>
> You seem to be hinting the former, but I do not think "the task was
> done" is the case here.
I think that this is a stale todo.
The only place there is a mention of temporary branches (which
is then parenthetically called a topic branch) is in relation to how Tony Luck organizes his work.
Additionally there is already a subsection on using a detatched head ("Examining an
old version without creating a new branch).
If there is more that was wanted, then I would be glad to add something, but
I don't see that there are references to remove.
>
> > Signed-off-by: Stephen P. Smith <ischis2@cox.net>
> > ---
> >
> > Notes:
> > A search of the user manual found only one location which refers to
> > temporary branches. This has to do with how Tony Luck uses them.
> >
> > Even then there is a clarifying parenthetical noting that the
> > temporary branches are topic branches.
> >
> > A git blame showed that the last time that the entry was updated was
> > in 2007.
> >
> > 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?
> > -
>
> What does "beginning" refer to in this sentence, though?
I had that question too even after looking at the 2007 version of the manual.
>
> After a quick reading of the beginning part of the document, I am
> getting the impression that it refers to the use of the 'new'
> branch, which is initially created out of v2.6.13 and then later
> reset to v2.6.17 while the user is in the sightseeing mode. And
> this way of working _is_ a remnant from the days back when detached
> HEAD was not with us.
>
> It is a completely separate matter if it is a good idea to teach
> detached HEAD that early in the tutorial, though.
So are you suggesting a move of the section further down?
Or are you suggesting that that is excised from the manual?
> So "remove the task because detached HEAD is a bit too weird thing to learn in that
> early stage in the learning curve" (i.e. the latter reason) might
> apply.
Could it be there are two reasons to remove the todo?
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-12-28 6:02 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 [this message]
2015-12-28 17:29 ` Junio C Hamano
2015-12-28 20:16 ` [PATCH V2] " Stephen P. Smith
2015-12-28 18:41 ` [PATCH] " 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=3065044.ki4VpYSZvR@thunderbird \
--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).