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

[PATCH v2 0/1] FAQ for common user questions

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Mar 25, 2020, 01:34 UTC
Message-ID
<20200325013434.219775-1-sandals@crustytoothpaste.net>

Git is an enormously flexible and powerful piece of software, but many people find it confusing and hard to use. This patch introduces a FAQ to address some common user questions and hopefully make it easier.

I know there are some plans to add additional entries to this. I propose we tack them on as additional patches, and if I need to reroll this again, I can pick them up as part of the series, unless someone has strong opinions about doing things differently.

Changes from v1:
* Fix various indentation issues.
* Avoid using "some people", except to state that "some people find `vi`
  difficult to use", preferring to use language addressing
  misconceptions more directly.
* Add "erroneously" to "This is often suggested" to avoid users
  accidentally doing what we recommend against.
* Attempt to come up with a better way to describe a personal name,
  using Junio as an example.
brian m. carlson (1):
  docs: add a FAQ
 Documentation/Makefile   |   1 +
 Documentation/gitfaq.txt | 337 +++++++++++++++++++++++++++++++++++++++
 2 files changed, 338 insertions(+)
 create mode 100644 Documentation/gitfaq.txt
Next: brian m. carlson
Message 1 of 6 in “FAQ for common user questions”
  1. 0/1 FAQ for common user questionsbrian m. carlson, Mar 25, 2020
  2. docs: add a FAQbrian m. carlson, Mar 25, 2020
  3. Martin ÅgrenMar 25, 2020
  4. brian m. carlsonMar 25, 2020
  5. Martin ÅgrenMar 25, 2020
  6. Junio C HamanoMar 25, 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.