From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 6/7] user-manual: add global config section
Date: Fri, 01 May 2009 17:16:18 -0700 [thread overview]
Message-ID: <7vfxfotl4d.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <94a0d4530905011551r635a4ebfrba86707419e13cc4@mail.gmail.com> (Felipe Contreras's message of "Sat, 2 May 2009 01:51:37 +0300")
Felipe Contreras <felipe.contreras@gmail.com> writes:
>> 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.
next prev parent reply other threads:[~2009-05-02 0:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-04 9:38 [PATCH 0/7] user-manual: general improvements Felipe Contreras
2009-04-04 9:38 ` [PATCH 1/7] user-manual: remove some git-foo usage Felipe Contreras
2009-04-04 9:38 ` [PATCH 2/7] docbook: improve css style Felipe Contreras
[not found] ` <1238837909-3060-4-git-send-email-felipe.contreras@gmail.com>
2009-04-04 9:38 ` [PATCH 4/7] user-manual: use 'fast-forward' instead of 'fast forward' Felipe Contreras
2009-04-04 9:38 ` [PATCH 5/7] user-manual: use SHA-1 instead of SHA1 or sha1 Felipe Contreras
2009-04-04 9:38 ` [PATCH 6/7] user-manual: add global config section Felipe Contreras
2009-04-04 9:38 ` [PATCH 7/7] user-manual: simplify the user configuration Felipe Contreras
2009-04-05 3:36 ` Jay Soffian
2009-04-05 9:14 ` Felipe Contreras
2009-04-05 15:11 ` Jay Soffian
2009-04-05 9:47 ` [PATCH 6/7] user-manual: add global config section Junio C Hamano
2009-05-01 8:37 ` Felipe Contreras
2009-05-01 22:08 ` Junio C Hamano
2009-05-01 22:51 ` Felipe Contreras
2009-05-02 0:16 ` Junio C Hamano [this message]
2009-04-06 8:14 ` [PATCH 5/7] user-manual: use SHA-1 instead of SHA1 or sha1 Junio C Hamano
2009-05-01 8:26 ` Felipe Contreras
2009-04-06 8:14 ` [PATCH 4/7] user-manual: use 'fast-forward' instead of 'fast forward' Junio C Hamano
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=7vfxfotl4d.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--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).