git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] RelNotes: Spelling & grammar fixes.

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Nov 18, 2013, 19:58 UTC
Message-ID
<20131118195827.GI27781@google.com>
In-Reply-To
<xmqqmwl1blg7.fsf@gitster.dls.corp.google.com>
Junio C Hamano wrote:
> Marc Branchaud <marcnarc@xiplink.com> writes:
Show 16 quoted lines
>>   * "git branch -v -v" (and "git status") did not distinguish among a
>> -   branch that does not build on any other branch, a branch that is in
>> -   sync with the branch it builds on, and a branch that is configured
>> -   to build on some other branch that no longer exists.
>> +   branch that is not tracking any other branch, a branch that is in
>> +   sync with the branch it is tracking, and a branch that is tracking
>> +   some other branch that no longer exists.
>
> People use the verb "track" to mean too many different things, and
> the original deliberately tried to avoid use of that word.
>
> Specifically, we try to limit the use of "track" to mean "to keep a
> copy of what we observed from the remote" as in "remote-tracking
> branch remotes/origin/master is used to track the 'master' branch at
> your 'origin'", which is very different from "your 'master' branch
> builds on your upstream's 'master'".

How about something like the following, in the same spirit as --track giving way to --set-upstream-to)?

	* "git branch -v -v" and "git status" did not distinguish among a
	  branch that does not have a corresponding upstream branch, a
	  branch that is in sync with its upstream, and a branch whose
	  upstream no longer exists.
Previous: Junio C Hamano
Message 12 of 12 in “[ANNOUNCE] Git v1.8.5-rc2”
  1. Junio C HamanoNov 13, 2013
  2. Marc BranchaudNov 14, 2013
  3. Junio C HamanoNov 18, 2013
  4. Junio C HamanoNov 18, 2013
  5. Marc BranchaudNov 18, 2013
  6. RelNotes: Spelling & grammar fixes.Marc Branchaud, Nov 14, 2013
  7. Marc BranchaudNov 15, 2013
  8. Junio C HamanoNov 18, 2013
  9. Marc BranchaudNov 18, 2013
  10. Jonathan NiederNov 18, 2013
  11. Junio C HamanoNov 18, 2013
  12. Jonathan NiederNov 18, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.