How log log a feaure request

How log log a feaure request

[Tymek Majewski]

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)?

----

What is the feature request?

Change git checkout's
"Your branch is up to date with 'origin/branch_name_here'"
(and similar messages)
to
"Your branch is up to date with the *local* branch 'origin/branch_name_here'"

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.


Cheers
Tymek

Re: How log log a feaure request

[Junio C Hamano]

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.

Re: How log log a feaure request

[Philip Oakley]

Hi Tymek, Junio

On 09/01/2020 04:44, Junio C Hamano wrote:
> 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". 
Can I agree to both aspects? Yes, the git terminology is "remote
tracking branch", but also that the term is very confusing because it is
not actually remote. It is held on the local machine, may not be up to
date, and doesn't check.

>  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.
If we need to explain this then perhaps we haven't been good at naming.
It took me a very long while to appreciate it was all backwards as its a
(local) branch that tracks a remote [sort of reverse Polish notation, or
French 'de' notation (OTAN/NATO)].

>
> 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 
I think we have a 'continue to be confused' possibility here.

> to seeing it and knowing what
> it is, and after all no user will stay to be a newbie forever.
I'm sure that for all those who have worked with Git from early days are
quite happy with the rtb notation (it was learnt as it developed), but I
feel that newer users who have arrived from always-on central-server
environments are having multiple challenges all arriving at same time,
so aren't learning.
> 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.
True. Perhaps move the "Your" from the beginning of the sentence, to the
end?

"Branch is up to date with your 'origin/branch_name_here'" or
"This branch is up to date with your 'origin/branch_name_here'"

>
> So... I dunno.
--
Philip
(still catching up with the list)