From: "J. Bruce Fields" <bfields@fieldses.org>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC/PATCH 7/8] user-manual: add global config section
Date: Tue, 24 Mar 2009 17:52:23 -0400 [thread overview]
Message-ID: <20090324215223.GL19389@fieldses.org> (raw)
In-Reply-To: <1237745121-6325-8-git-send-email-felipe.contreras@gmail.com>
On Sun, Mar 22, 2009 at 08:05:20PM +0200, Felipe Contreras wrote:
> Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
> ---
> Documentation/user-manual.txt | 34 ++++++++++++++++++++++++++++++++++
> 1 files changed, 34 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
> index 3278aa7..b7678aa 100644
> --- a/Documentation/user-manual.txt
> +++ b/Documentation/user-manual.txt
> @@ -40,6 +40,40 @@ without any explanation.
> Finally, see <<todo>> for ways that you can help make this manual more
> complete.
>
> +[[getting-started]]
> +Getting started
> +=============
> +
> +You can skip this section safely, however, configuring git at an early stage
> +would probably make your overall experience with it more pleasant. Also many
> +parts on this manual would be easier to grasp.
I'd skip this first paragraph.
> +
> +Git's configuration is distributed on different locations: 'system', 'global', and
> +'repository'. Variables are stored in the form of 'foo.bar', and the precedence
> +order is 'repository' > 'global' > 'system'.
"distributed on" isn't right ("among" instead of "on" might work). It's
not obvious to me what ">" means in terms of precedence. And I'm not
sure the comment about the form conveys any useful information. Also, I
think the systemwide configuration is less important, and could be left
to the man page.
> +
> +You would probably want to start setting up something useful:
> +------------------------------------------------
> +$ git config --global color.ui auto
> +------------------------------------------------
> +
> +This will make prettier the output of certain commands such as `git diff`, but
> +that's not important; what is important here is that `color.ui` has been
> +stored in the 'global' (for the user) configuration.
> +
> +You can take a look and manually modify the configuration with the `--edit`
"take a look and" isn't really necessary; either eliminate it or replace
it by "view and" or just "also".
> +option (will use '$EDITOR'):
s/will/which will/.
--b.
> +------------------------------------------------
> +$ git config --global --edit
> +[color]
> + ui = auto
> +------------------------------------------------
> +
> +Or you can manually edit the file which is located in `~/.gitconfig`. Other
> +locations are `/etc/gitconfig` (system), and `.git/config` (repository).
> +
> +Other git configurations will be covered in the rest of the manual, if you
> +want to learn more look at linkgit:git-config[1] for details.
>
> [[repositories-and-branches]]
> Repositories and Branches
> --
> 1.6.2.1.352.gae594
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-03-24 21:53 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-22 18:05 [RFC/PATCH 0/8] user-manual: style improvements Felipe Contreras
2009-03-22 18:05 ` [RFC/PATCH 1/8] user-manual: remove some git-foo usage Felipe Contreras
2009-03-22 18:05 ` [RFC/PATCH 2/8] docbook: improve css style Felipe Contreras
2009-03-22 18:05 ` [RFC/PATCH 3/8] docbook: radical style change Felipe Contreras
[not found] ` <1237745121-6325-5-git-send-email-felipe.contreras@gmail.com>
2009-03-22 18:05 ` [RFC/PATCH 5/8] user-manual: use 'fast-forward' instead of 'fast forward' Felipe Contreras
2009-03-22 18:05 ` [RFC/PATCH 6/8] user-manual: use SHA-1 instead of SHA1 or sha1 Felipe Contreras
2009-03-22 18:05 ` [RFC/PATCH 7/8] user-manual: add global config section Felipe Contreras
2009-03-22 18:05 ` [RFC/PATCH 8/8] user-manual: simplify the user configuration Felipe Contreras
2009-03-22 22:42 ` Wincent Colaiuta
2009-03-22 23:01 ` Felipe Contreras
2009-03-23 0:00 ` Junio C Hamano
2009-03-23 11:02 ` Felipe Contreras
2009-03-23 0:07 ` Wincent Colaiuta
2009-03-23 11:07 ` Felipe Contreras
2009-03-23 11:09 ` Wincent Colaiuta
2009-03-24 0:22 ` Felipe Contreras
2009-03-24 21:52 ` J. Bruce Fields [this message]
2009-03-24 22:17 ` [RFC/PATCH 7/8] user-manual: add global config section Felipe Contreras
2009-03-24 22:42 ` J. Bruce Fields
2009-03-23 6:50 ` [RFC/PATCH 3/8] docbook: radical style change Jeff King
2009-03-23 10:47 ` Felipe Contreras
2009-03-23 6:42 ` [RFC/PATCH 2/8] docbook: improve css style Jeff King
2009-03-23 10:31 ` Felipe Contreras
2009-03-23 15:20 ` Michael J Gruber
2009-03-24 0:21 ` Felipe Contreras
2009-03-24 2:08 ` Junio C Hamano
2009-03-24 7:52 ` Felipe Contreras
2009-03-24 8:18 ` Jeff King
2009-03-24 8:57 ` Felipe Contreras
2009-03-24 9:00 ` Jeff King
2009-03-24 9:39 ` Felipe Contreras
2009-03-24 8:29 ` Michael J Gruber
2009-03-24 9:06 ` Felipe Contreras
2009-03-24 9:16 ` Jeff King
2009-03-24 10:39 ` Michael J Gruber
2009-03-24 10:52 ` Felipe Contreras
2009-03-24 0:20 ` Felipe Contreras
2009-03-24 8:42 ` Jeff King
2009-03-23 6:31 ` [RFC/PATCH 1/8] user-manual: remove some git-foo usage Jeff King
2009-03-23 10:54 ` Felipe Contreras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090324215223.GL19389@fieldses.org \
--to=bfields@fieldses.org \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).