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

Re: [PATCH 1/2] fetch: add missing documentation

From
Jeff King <peff@peff.net>
Date
Sep 24, 2013, 06:54 UTC
Message-ID
<20130924065454.GB7257@sigill.intra.peff.net>
In-Reply-To
<CAMP44s23FMeZP=xum1X9bvHuKVo=j8O=8_8DVNgXq9F7Cpsr7A@mail.gmail.com>
On Tue, Sep 24, 2013 at 01:31:48AM -0500, Felipe Contreras wrote:
Show 10 quoted lines
> > I don't think it is the end of the world if we say "upstream branch". I
> > was hoping to find a term that could be both friendly and accurate.
> >
> > And failing that, I hoped you might say "I see what you are saying, but
> > I cannot think of a term that is more precise that does not sacrifice
> > friendliness". But as I seem incapable of even communicating the issue
> > to you, I'm giving up. It is not worth wasting more time on it.
> 
> And I was hoping you wouldn't use rhetorical warfare and label things
> as "inaccurate", "imprecise", "breadcrumbs".

FWIW, the term "breadcrumbs" was meant as a _good_ thing. I meant that you are using a term that will link the user to other concepts that use the same term (like "branch --set-upstream-to"), and that is something we would like to keep.

As for the others, I find your accusation of rhetorical warfare ridiculous. Insulting your patch with non-constructive insults would be rhetorical. Saying "I think it has a flaw, here are my reasons, and I hope we can come up with a solution that does not have that flaw without weakening the other properties" is collaboration. Or an attempt at it anyway.

I do not know why you and I have so much trouble communicating on even basic things. I am willing to accept that it is entirely my fault. But that does not change the fact that I often find it a waste of time, and I plan to do less of it by ending my involvement in threads that seem to be unproductive.

> At this porcelain level, branch.<name>.remote does not exist, so
> "upstream branch" is accurate. Period.

I do not agree with your first sentence at all. And your second one is purely rhetorical.

I can elaborate if you really care, but I have a feeling you do not.
-Peff
Previous: Felipe ContrerasNext: Felipe Contreras
Message 11 of 15 in “fetch: trivial fixes”
  1. 0/2 fetch: trivial fixesFelipe Contreras, Sep 21, 2013
  2. 1/2 fetch: add missing documentationFelipe Contreras, Sep 21, 2013
  3. Jeff KingSep 24, 2013
  4. Felipe ContrerasSep 24, 2013
  5. Jeff KingSep 24, 2013
  6. Felipe ContrerasSep 24, 2013
  7. Jeff KingSep 24, 2013
  8. Felipe ContrerasSep 24, 2013
  9. Jeff KingSep 24, 2013
  10. Felipe ContrerasSep 24, 2013
  11. Jeff KingSep 24, 2013
  12. Felipe ContrerasSep 24, 2013
  13. 2/2 remote: fix trivial memory leakFelipe Contreras, Sep 21, 2013
  14. Jeff KingSep 24, 2013
  15. Junio C HamanoOct 15, 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.