git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: A simpler approach to tracking directories (was: The philosophy behind my directory proposal in a nutshell)
Date: Sun, 22 Jul 2007 20:13:23 +0200	[thread overview]
Message-ID: <f806bb$ib1$1@sea.gmane.org> (raw)
In-Reply-To: 20070722175731.GA16658@thunk.org

Theodore Tso wrote:

> Another way of putting is this single bit of information meaning "keep
> this directory around when empty" is something that ***must*** be
> representable in three different places: in a git tree object, in the
> index, *AND* in the working tree.  The problem with "." is that since
> all directories contain the "." entry, you can't represent the bit of
> information you want to record in the working tree in that way.

I don't think the "do not delete when empty" bit must be somehow represented
in the working directory. It is enough to have this bit in index to deal
with working directory, and in the repository to have it persistent.

Compare with submodules, and with unmerged entries (which sometimes do not
have worktree representation).

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git

  reply	other threads:[~2007-07-22 18:06 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 [this message]
2007-07-22 18:45     ` A simpler approach to tracking directories David Kastrup
2007-07-22 21:45       ` J. Bruce Fields

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='f806bb$ib1$1@sea.gmane.org' \
    --to=jnareb@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).