From: Junio C Hamano <gitster@pobox.com>
To: Tymek Majewski <tmaj@pm.me>
Cc: "git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: How log log a feaure request
Date: Wed, 08 Jan 2020 20:44:29 -0800 [thread overview]
Message-ID: <xmqq1rs91bo2.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <l0W9VY7TaoqT51RecilbNNTaX35RiCNlJtZKcz04cyKexuG06-bZMlwfor5kCvnIHRRWE7s8TSJLwvA-w4-1poMV_gle8iOzd3-wzFVDUh0=@pm.me> (Tymek Majewski's message of "Thu, 09 Jan 2020 02:06:41 +0000")
Tymek Majewski <tmaj@pm.me> writes:
> Hello gurus!
>
> I looked at https://git-scm.com/community but I failed to find a
> place to send feature requests to.
>
> Q: How to submit a feature request (rather than a bug)?
Sending it here, which you did, is how ;-)
> Reasoning:
>
> I believe that if the git checkout message
> "Your branch is up to date with 'origin/branch_name_here'"
> was
> "Your branch is up to date with the *local* branch 'origin/branch_name_here'"
> it would make it clearer to new users what is happening.
I would be sympathetic to the above, if you did not say "local" and
instead say "remote-tracking". A local branch is what you can check
out and grow its history by making a commit while it is checked out.
Those refs that are updated when you fetch and/or pull from the
remote repository in order to keep track of the branches they have
are called remote-tracking branches.
Because this message is something people see every day when they run
"git checkout", I am not sure if the extra explanation is warranted
or merely annoying, as "origin/branch" notation is used sufficiently
often for the users to grow accustomed to seeing it and knowing what
it is, and after all no user will stay to be a newbie forever.
Another reason why I am somewhat hesitant to endorse the rephrasing
is because the name of a remote-tracking branch in the real life
tends to be longer than just 'origin/master'. We must keep the
message that comes before the name of the remote-tracking branch
short in order to make it easier to read the message for the users.
So... I dunno.
next prev parent reply other threads:[~2020-01-09 4:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 2:06 How log log a feaure request Tymek Majewski
2020-01-09 4:44 ` Junio C Hamano [this message]
2020-03-28 11:38 ` Philip Oakley
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq1rs91bo2.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=tmaj@pm.me \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).