From: "Randall S. Becker" <rsbecker@nexbridge.com>
To: "'Robert P. J. Day'" <rpjday@crashcourse.ca>,
"'Git Mailing list'" <git@vger.kernel.org>
Subject: RE: which files are "known to git"?
Date: Mon, 21 May 2018 09:58:09 -0400 [thread overview]
Message-ID: <000201d3f10b$c3bfd660$4b3f8320$@nexbridge.com> (raw)
In-Reply-To: <alpine.LFD.2.21.1805210717040.9926@localhost.localdomain>
On May 21, 2018 7:19 AM, Robert P. J. Day:
> updating my git courseware and, since some man pages refer to files
> "known to git", i just want to make sure i understand precisely which
files
> those are. AIUI, they would include:
>
> * tracked files
> * ignored files
> * new files which have been staged but not yet committed
You might want to consider git metadata/config/attribute files, hooks,
filters, etc., that may not be not formally part of a repository, but can be
required to ensure the content is complete.
Cheers,
Randall
-- Brief whoami:
NonStop developer since approximately 211288444200000000
UNIX developer since approximately 421664400
-- In my real life, I talk too much.
next prev parent reply other threads:[~2018-05-21 13:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 11:18 which files are "known to git"? Robert P. J. Day
2018-05-21 13:58 ` Randall S. Becker [this message]
2018-05-21 15:09 ` Elijah Newren
2018-05-21 15:18 ` Duy Nguyen
2018-05-21 15:49 ` Robert P. J. Day
2018-05-21 15:53 ` Robert P. J. Day
2018-05-21 16:08 ` Junio C Hamano
2018-05-21 17:40 ` Robert P. J. Day
2018-05-21 17:53 ` Jonathan Nieder
2018-05-21 18:09 ` Robert P. J. Day
2018-05-21 18:15 ` Jonathan Nieder
2018-05-22 2:14 ` Junio C Hamano
2018-05-23 8:20 ` Robert P. J. Day
2018-05-21 18:13 ` Elijah Newren
2018-05-21 18:14 ` Robert P. J. Day
2018-05-21 18:15 ` Stefan Beller
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='000201d3f10b$c3bfd660$4b3f8320$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.