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

RE: [PATCH] doc: reword gitworflows for neutrality

From
BENSOUSSAN--BOHM DANIEL p1507430 <daniel.bensoussan--bohm@etu.univ-lyon1.fr>
Date
Dec 10, 2017, 11:58 UTC
Message-ID
<1512907098563.90200@etu.univ-lyon1.fr>
In-Reply-To
<CAPig+cTgJepi6xVn0+qP3SW0Y0g-6Nf4LvCjCkvEHfZwugY1Hg@mail.gmail.com>
>As a native English speaker, I find the new phrasing odd, and think
>this may a step backward. How about trying a different approach? For
>example:
    >Occasionally, the maintainer may get merge conflicts when trying
    >to pull changes from downstream. In this case, it may make sense
    >to ask downstream to do the merge and resolve the conflicts
    >instead (since, presumably, downstream will know better how to
    >resolve them).
Indeed, this is an other possibility.
Thanks for the review.
Daniel BENSOUSSAN-BOHM
Previous: Eric Sunshine
Message 3 of 3 in “doc: reword gitworflows for neutrality”
  1. doc: reword gitworflows for neutralityDaniel Bensoussan, Dec 8, 2017
  2. Eric SunshineDec 8, 2017
  3. BENSOUSSAN--BOHM DANIEL p1507430Dec 10, 2017

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.