git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brown <git@davidb.org>
To: Asheesh Laroia <asheesh@asheesh.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: why still no empty directory support in git
Date: Tue, 30 Dec 2008 17:06:20 -0800	[thread overview]
Message-ID: <20081231010620.GA26997@linode.davidb.org> (raw)
In-Reply-To: <alpine.DEB.2.00.0812300346040.19911@vellum.laroia.net>

On Tue, Dec 30, 2008 at 03:58:46AM -0500, Asheesh Laroia wrote:

> This is because git is removing these directories. There is a strict 
> incompatibility between git rmdir()ing empty directories behind my back and 
> Maildir systems.

So, would there be a hook that would run at all of the times git might
remove the directories, and the hook could just put them back if
missing?

The post-merge hook is certainly one place, but there are likely
others.  You might also want one in post-checkout, but I'm guessing
that switching branches is going to be less frequent in a maildir
directory.

David

  reply	other threads:[~2008-12-31  1:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-30  3:42 why still no empty directory support in git Ping Yin
2008-12-30  5:10 ` Asheesh Laroia
2008-12-30  5:28   ` Jeff Whiteside
2008-12-30  6:58     ` Robin Rosenberg
2008-12-30  7:45       ` Junio C Hamano
2008-12-30 15:36       ` Ping Yin
2008-12-30  6:25   ` Asheesh Laroia
2008-12-30  8:43     ` demerphq
2008-12-30  8:58       ` Asheesh Laroia
2008-12-31  1:06         ` David Brown [this message]
2009-01-01 20:06         ` Jeff King
2009-01-02 18:55           ` Johannes Schindelin
2009-01-02 21:31             ` Asheesh Laroia
2009-01-08  7:12           ` Asheesh Laroia
2008-12-30  6:09 ` Liu Yubao
2009-01-01  2:50   ` Anatol Pomozov
2008-12-30 12:09 ` Johannes Schindelin
2008-12-30 14:21   ` Michael Gaber

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=20081231010620.GA26997@linode.davidb.org \
    --to=git@davidb.org \
    --cc=asheesh@asheesh.org \
    --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).