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

Re: [PATCH 6/7] user-manual: add global config section

From
Junio C Hamano <gitster@pobox.com>
Date
May 2, 2009, 00:16 UTC
Message-ID
<7vfxfotl4d.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<94a0d4530905011551r635a4ebfrba86707419e13cc4@mail.gmail.com>
Felipe Contreras <felipe.contreras@gmail.com> writes:
Show 15 quoted lines
>> A good sequence would be:
>>
>>        To start working on a tarball extract (or your uncontrolled
>>        project) with git, first do:
>>
>>        $ git init
>>
>>        Whoa.  That was fast.  Did it do anything?  Yes, it created a
>>        subdirectory .git that is going to store your history and other
>>        control information.  Right now you do not have any history (nor
>>        the current state for that matter) recorded in it, but it already
>>        has some control information.  One of the more important one is
>>        the per-repository configuration file.  Take a look:
> ...
> Most people don't start with 'git init' they start with 'git clone'

That does not just not change the issue but even strengthens my point. After clone, you have a working per-repository .git/config file that is a good demonstration of how easy and simple the syntax is. You of course need to adjust the prose to guide the user to the configuration file if you use clone instead of init, but that goes without saying.

By the way, I think you lacked 1/4 in your last round and this time it is missing too.

[  17: Felipe Contreras  ] [PATCH v2 0/4] user-manual: general impro
[  74: Felipe Contreras  ] [PATCH v2 2/4] user-manual: use 'fast-for
 [  51: Felipe Contreras  ] [PATCH v2 3/4] user-manual: add global c
  [  38: Felipe Contreras  ] [PATCH v2 4/4] user-manual: simplify th

The description in 0/4 makes it sound like 1/4 is a general clean-up improvement, and so is 2/4. Can we apply these two first (and we obviously need to find that missing 1/4 --- is there some git-send-email bug hiding or something)?

The two patches 3/4 and 4/4 are not "general" improvement; it is to advocate the use of "git config" more instead of showing the file in the editor, and while you obviously think it is an improvement, I do not think there is a "general" consensus that it is an improvement.

More importantly, I do not think that is integral part of the "general clean-up", and by making it a separate topic, we can shrink the size of the patches in flight.

Previous: Felipe ContrerasNext: Junio C Hamano
Message 15 of 18 in “user-manual: general improvements”
  1. 0/7 user-manual: general improvementsFelipe Contreras, Apr 4, 2009
  2. 1/7 user-manual: remove some git-foo usageFelipe Contreras, Apr 4, 2009
  3. 2/7 docbook: improve css styleFelipe Contreras, Apr 4, 2009
  4. 4/7 user-manual: use 'fast-forward' instead of 'fast forward'Felipe Contreras, Apr 4, 2009
  5. 5/7 user-manual: use SHA-1 instead of SHA1 or sha1Felipe Contreras, Apr 4, 2009
  6. 6/7 user-manual: add global config sectionFelipe Contreras, Apr 4, 2009
  7. 7/7 user-manual: simplify the user configurationFelipe Contreras, Apr 4, 2009
  8. Jay SoffianApr 5, 2009
  9. Felipe ContrerasApr 5, 2009
  10. Jay SoffianApr 5, 2009
  11. Junio C HamanoApr 5, 2009
  12. Felipe ContrerasMay 1, 2009
  13. Junio C HamanoMay 1, 2009
  14. Felipe ContrerasMay 1, 2009
  15. Junio C HamanoMay 2, 2009
  16. Junio C HamanoApr 6, 2009
  17. Felipe ContrerasMay 1, 2009
  18. Junio C HamanoApr 6, 2009

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.