From: "J. Bruce Fields" <bfields@fieldses.org>
To: David Kastrup <dak@gnu.org>
Cc: Theodore Tso <tytso@mit.edu>, git@vger.kernel.org
Subject: Re: A simpler approach to tracking directories
Date: Sun, 22 Jul 2007 17:45:40 -0400 [thread overview]
Message-ID: <20070722214540.GA821@fieldses.org> (raw)
In-Reply-To: <85myxoi8fi.fsf@lola.goethe.zz>
On Sun, Jul 22, 2007 at 08:45:37PM +0200, David Kastrup wrote:
> Theodore Tso <tytso@mit.edu> writes:
> > One of the fundamental things which falls out of the "Git Tracks
> > Contents" mantra is that information which you expect to be pushed
> > forward future revisions (as opposed to metadata which is specific
> > to a commit, such as the Author and Committer of a patch, the Commit
> > log, etc.) *MUST* be information which is realized in the working
> > tree.
>
> For every _file_ in the working tree, there is _one_ bit of
> information in the repository that is not in the working tree: namely
> whether git is tracking this file at all.
Actually, no. The index just stores data for a given set of files. You
can think of the set of files for which data is stored in the index as
the set that is "tracked", but there's no independent
"tracked/untracked" bit, and no way of marking a path as tracked without
also adding content at that path.
--b.
prev parent reply other threads:[~2007-07-22 21:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-21 22:22 The philosophy behind my directory proposal in a nutshell David Kastrup
2007-07-21 23:40 ` git-rm semantics (was: The philosophy behind my directory proposal in a nutshell) David Kastrup
2007-07-22 15:39 ` A simpler approach to tracking directories " David Kastrup
2007-07-22 17:57 ` Theodore Tso
2007-07-22 18:13 ` Jakub Narebski
2007-07-22 18:45 ` A simpler approach to tracking directories David Kastrup
2007-07-22 21:45 ` J. Bruce Fields [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070722214540.GA821@fieldses.org \
--to=bfields@fieldses.org \
--cc=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=tytso@mit.edu \
/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).