git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: as promised, docs: git for the confused
Date: 13 Dec 2005 05:58:41 -0800	[thread overview]
Message-ID: <861x0hxfn2.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <7vd5k1bf40.fsf@assigned-by-dhcp.cox.net>

>>>>> "Junio" == Junio C Hamano <junkio@cox.net> writes:

Junio> Junio C Hamano <junkio@cox.net> writes:
>> The only Plumbing support is that ls-files takes --exclude-from=
>> and --exclude-per-directory= options.  It is up to the Porcelain
>> layer what names to use.
>> 
>> We agreed upon a convention to use .gitignore as per-directory
>> and .git/info/exclude (I think this came from existing practice
>> by Cogito back then) as the tree-wide fallback, when these two
>> flags were introduced to ls-files, for interoperability across
>> Porcelains.

Junio> ... and as Linus pointed out already, the barebone Porcelain-ish
Junio> that ship with git follows that convention as well.

I see now that grepping "gitignore" shows git-add.sh and
git-status.sh.  gitignore is indeed doc'ed in git-add.txt, but not in
git-status.txt.  Must've snuck in recently.  I'm trying to watch
"git-whatchanged -p Documentation/*", but I miss things sometimes.

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

  reply	other threads:[~2005-12-13 13:58 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7vbqzrcmgr.fsf@assigned-by-dhcp.cox.net>
2005-12-09  5:43 ` as promised, docs: git for the confused linux
2005-12-09  9:43   ` Petr Baudis
2005-12-09 14:01     ` linux
2005-12-09 16:49       ` Randy.Dunlap
2005-12-09 19:12       ` Junio C Hamano
2005-12-09 21:54         ` linux
2005-12-09 23:23           ` Junio C Hamano
2005-12-12 16:34             ` Linus Torvalds
2005-12-12 17:53               ` Timo Hirvonen
2005-12-12 18:18                 ` Linus Torvalds
2005-12-12 20:39                   ` Randal L. Schwartz
2005-12-13  3:58                     ` Joshua N Pritikin
2005-12-13  3:59                       ` Randal L. Schwartz
2005-12-13  5:19                         ` Junio C Hamano
2005-12-13  5:29                           ` Linus Torvalds
2005-12-13  7:18                             ` H. Peter Anvin
2005-12-13  8:01                           ` Junio C Hamano
2005-12-13 13:58                             ` Randal L. Schwartz [this message]
2005-12-13 21:16                               ` Tip of the day: archaeology Junio C Hamano
2005-12-13 21:54                                 ` Linus Torvalds
2005-12-13 22:19                                   ` Junio C Hamano
2005-12-12 17:54               ` as promised, docs: git for the confused Junio C Hamano
2005-12-13  0:22               ` [PATCH] Everyday: some examples Junio C Hamano
2005-12-09 21:33       ` as promised, docs: git for the confused Petr Baudis
2005-12-09  5:44 ` linux
2005-12-10  1:22   ` Junio C Hamano
2005-12-10  8:00   ` Junio C Hamano
2005-12-10 10:56     ` linux
2005-12-04 21:34 git-name-rev off-by-one bug Petr Baudis
2005-12-08  6:34 ` as promised, docs: git for the confused linux
2005-12-08 21:53   ` Junio C Hamano
2005-12-08 22:02     ` H. Peter Anvin
2005-12-09  0:47   ` Alan Chandler
2005-12-09  1:45     ` Petr Baudis
2005-12-09  1:19   ` Josef Weidendorfer

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=861x0hxfn2.fsf@blue.stonehenge.com \
    --to=merlyn@stonehenge.com \
    --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.
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).