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

Re: [PATCH 0/3] FAQ entries for merges and modified files

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 12, 2020, 21:48 UTC
Message-ID
<xmqqwo0ymzu2.fsf@gitster.c.googlers.com>
In-Reply-To
<20200912204824.2824106-1-sandals@crustytoothpaste.net>
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> This series introduces a few new FAQ entries on various topics.
All look like topics worth covering.
Thanks.
Previous: brian m. carlsonNext: brian m. carlson
Message 9 of 13 in “FAQ entries for merges and modified files”
  1. 0/3 FAQ entries for merges and modified filesbrian m. carlson, Sep 12, 2020
  2. 3/3 docs: explain how to deal with files that are always modifiedbrian m. carlson, Sep 12, 2020
  3. Martin ÅgrenSep 13, 2020
  4. 2/3 docs: explain why reverts are not always applied on mergebrian m. carlson, Sep 12, 2020
  5. Martin ÅgrenSep 13, 2020
  6. 1/3 docs: explain why squash merges are broken with long-running branchesbrian m. carlson, Sep 12, 2020
  7. Martin ÅgrenSep 13, 2020
  8. brian m. carlsonSep 13, 2020
  9. Junio C HamanoSep 12, 2020
  10. 0/3 FAQ entries for merges and modified filesbrian m. carlson, Sep 20, 2020
  11. 2/3 docs: explain why reverts are not always applied on mergebrian m. carlson, Sep 20, 2020
  12. 1/3 docs: explain why squash merges are broken with long-running branchesbrian m. carlson, Sep 20, 2020
  13. 3/3 docs: explain how to deal with files that are always modifiedbrian m. carlson, Sep 20, 2020

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.