From: Johan Herland <johan@herland.net>
To: "J. Bruce Fields" <bfields@citi.umich.edu>
Cc: Junio C Hamano <junkio@cox.net>,
git@vger.kernel.org,
"J. Bruce Fields" <bfields@puzzle.fieldses.org>
Subject: Re: [PATCH 1/6] user-manual: edit "ignoring files" for conciseness
Date: Sun, 26 Aug 2007 12:57:24 -0700 [thread overview]
Message-ID: <200708261257.24338.johan@herland.net> (raw)
In-Reply-To: <11881450231606-git-send-email->
On Sunday 26 August 2007 09:16:57 J. Bruce Fields wrote:
> From: J. Bruce Fields <bfields@puzzle.fieldses.org>
>
> The immediate motivation for writing this section was to explain the
> various places ignore patterns could be used. However, I still think
> .gitignore is the case most people will want to learn about first. It
> also makes it a bit more concrete to introduce ignore patterns in the
> context of .gitignore first. And the existance of gitignore(5) relieves
> the pressure to explain it all here.
>
> So, stick to the .gitignore example, with only a brief mention of the
> others, explain the syntax only by example, and leave the rest to
> gitignore(5).
>
> Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
> Cc: Johan Herland <johan@herland.net>
Acked-By: Johan Herland <johan@herland.net>
Have fun!
...Johan
prev parent reply other threads:[~2007-08-26 20:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11881450221019-git-send-email->
[not found] ` <464a8a7a15fc70efbcf56c4569f0f7275a9c76fe.1188139206.git.bfields@citi.umich.edu>
2007-08-26 16:16 ` [PATCH 1/6] user-manual: edit "ignoring files" for conciseness J. Bruce Fields
[not found] ` <a5f90f31302eb47cb1aa2f12447376ff9332abef.1188139206.git.bfields@citi.umich.edu>
2007-08-26 16:16 ` [PATCH 2/6] user-manual: minor editing " J. Bruce Fields
[not found] ` <a2ef9d633f67edc227b00209d5b72ec388388877.1188139206.git.bfields@citi.umich.edu>
2007-08-26 16:16 ` [PATCH 3/6] user-manual: introduce the word "commit" earlier J. Bruce Fields
[not found] ` <e2618ff42716dd7cbc7a353670f46f357c5fb4c5.1188139206.git.bfields@citi.umich.edu>
2007-08-26 16:17 ` [PATCH 4/6] user-manual: use pithier example commit J. Bruce Fields
[not found] ` <d5821de2e29a3a207a2c5188f73b7d1f6d52fc34.1188139206.git.bfields@citi.umich.edu>
2007-08-26 16:17 ` [PATCH 5/6] user-manual: fix incorrect header level J. Bruce Fields
[not found] ` <a115daff12d8d26975ff15a4278a212df2c8c70b.1188139206.git.bfields@citi.umich.edu>
2007-08-26 16:17 ` [PATCH 6/6] Documentation/user-manual.txt: fix a few omissions of gitlink commands J. Bruce Fields
[not found] ` <11881450231606-git-send-email->
[not found] ` <11881450231010-git-send-email->
[not found] ` <11881450233251-git-send-email->
[not found] ` <11881450231946-git-send-email->
2007-08-26 19:57 ` Johan Herland [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200708261257.24338.johan@herland.net \
--to=johan@herland.net \
--cc=bfields@citi.umich.edu \
--cc=bfields@puzzle.fieldses.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).