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

Re: [RFC/PATCH] Triangular Workflow UI improvement: Documentation

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Jun 7, 2016, 07:03 UTC
Message-ID
<vpqportbhw4.fsf@anie.imag.fr>
In-Reply-To
<0B6B083EAEAA4E428C26CDAFE56E2FF6@PhilipOakley>
"Philip Oakley" <philipoakley@iee.org> writes:
Show 33 quoted lines
> From: "Matthieu Moy" <Matthieu.Moy@grenoble-inp.fr>
>
>> But then the maintainer is not the one picking changes from it (you're
>> sending them by email), so the "maintainer" label is not really accurate
>> in the diagram:
>>
>> +------------               -----------
>> +| UPSTREAM |  maintainer   | ORIGIN  |
>> +|  git/git |- - - - - - - -|  me/git |
>> +------------       ←       -----------
>> +         \                   /
>> +          \                 /
>> +     fetch↓\               /↑push
>> +            \             /
>> +             \           /
>> +             -------------
>> +             |   LOCAL   |
>> +             -------------
>>
> Ahh, that's a useful clarification. I use my git repo both for the G4W
> (which does take pull requests) and for Junio's Git.
>
> The use of the 'home-vault' fork as being for
> (a) backup,
> (b) open viewing, and
> (c) sending pull requests
> are subtle distinctions for the naming (of both the forked repo, and
> the workflow).
>
> It's probably even worse in a corporate environment as to how personal
> the personal home vault is, as compared to just having a namespace in
> a centralised dev server/repo. (the question of how to make such
> arrangements seems to come up moderately often on the various lists)

Yes, but again, the point of this thread is to document *one* workflow, not all possible uses of pushRemote. It's much easier to describe "one typical triangular workflow" in a concrete way than to try to be completely general and end up with a description that average users would just not understand.

It would be different to me if we were writting the pushRemote part of config.txt, where we have to be as general as possible.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: Philip OakleyNext: Philip Oakley
Message 20 of 41 in “[RFC] Triangular Workflow: user friendly full implementation”
  1. Jordan DE GEAMay 26, 2016
  2. Matthieu MoyMay 26, 2016
  3. Junio C HamanoMay 26, 2016
  4. [RFC] Triangular Workflow UI improvementJordan DE GEA, May 30, 2016
  5. Philip OakleyMay 27, 2016
  6. [RFC] Triangular Workflow UI improvmentsJordan DE GEA, May 30, 2016
  7. Triangular Workflow UI improvement: DocumentationJordan DE GEA, May 31, 2016
  8. Matthieu MoyMay 31, 2016
  9. Jordan DE GEAJun 1, 2016
  10. Michael HaggertyJun 2, 2016
  11. Philip OakleyJun 3, 2016
  12. Jordan DE GEAJun 3, 2016
  13. Matthieu MoyJun 3, 2016
  14. Jordan DE GEAJun 3, 2016
  15. Jordan DE GEAJun 5, 2016
  16. Matthieu MoyJun 6, 2016
  17. Philip OakleyJun 6, 2016
  18. Matthieu MoyJun 6, 2016
  19. Philip OakleyJun 6, 2016
  20. Matthieu MoyJun 7, 2016
  21. Philip OakleyJun 7, 2016
  22. Junio C HamanoJun 3, 2016
  23. Philip OakleyJun 3, 2016
  24. [RFC/PATCHv2] Documentation: triangular workflowJordan DE GEA, Jun 6, 2016
  25. Junio C HamanoJun 6, 2016
  26. Philip OakleyJun 6, 2016
  27. Matthieu MoyJun 7, 2016
  28. Jordan DE GEAJun 7, 2016
  29. [PATCHv3] Documentation: triangular workflowJordan DE GEA, Jun 7, 2016
  30. Junio C HamanoJun 7, 2016
  31. Jordan DE GEAJun 8, 2016
  32. Matthieu MoyJun 8, 2016
  33. [PATCHv4] Documentation: triangular workflowJordan DE GEA, Jun 9, 2016
  34. Junio C HamanoJun 9, 2016
  35. Ramkumar RamachandraJun 11, 2016
  36. Philip OakleyJun 11, 2016
  37. Philip OakleyJun 9, 2016
  38. Junio C HamanoJun 10, 2016
  39. Philip OakleyJun 11, 2016
  40. Junio C HamanoJun 13, 2016
  41. [RFC] Triangular Workflow UI improvementJordan DE GEA, May 30, 2016

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.