git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kevin P. Fleming" <kpfleming@digium.com>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: Jakub Narebski <jnareb@gmail.com>,
	Jonathan Nieder <jrnieder@gmail.com>,
	"Dmitry S. Kravtsov" <idkravitz@gmail.com>,
	git@vger.kernel.org, Shawn Pearce <spearce@spearce.org>
Subject: Re: Tracking empty directories
Date: Wed, 02 Feb 2011 06:31:38 -0600	[thread overview]
Message-ID: <4D494EAA.2060803@digium.com> (raw)
In-Reply-To: <AANLkTikkymYmnXh7XB1SM8br_oK-YmAJYfkwjTuLzr+f@mail.gmail.com>

On 02/01/2011 09:54 PM, Nguyen Thai Ngoc Duy wrote:
> On Wed, Feb 2, 2011 at 2:03 AM, Jakub Narebski<jnareb@gmail.com>  wrote:
>>> To add, one would use "git update-index --add".
>>
>> Porcelain version could be "git add -N<directory>", don't you agree?
>
> "git add" is recursive, with or without -N. What I worry is user
> accidentally "git add -N<dir>" where<dir>  is not empty, which adds
> everything in<dir>.
>
>>> The magic disappears when you register a file within that directory;
>>> to tell git you want to keep it, one would mkdir and
>>> "git update-index --add" again.  Once it's working, we can think about
>>> if there is a need for making that last step automatic after all
>>> (my guess: "no"). ;-)
>>
>> Hmmm... could we use mechanism similar to assume-unchanged to mark
>> directory as explicitely tracked, and that git should not remove it
>> when it becomes empty?
>
> I think git-attr suits better, more persistent. Although if you insist
> the directory must stay, why not just put a hidden file in there?

That's what I do now... in fact, since the empty directory needs to 
exist in checkouts *and* be empty, adding a .gitignore file with content 
'*' works quite well.

-- 
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
skype: kpfleming | jabber: kfleming@digium.com
Check us out at www.digium.com & www.asterisk.org

  reply	other threads:[~2011-02-02 13:02 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-29 10:01 Features from GitSurvey 2010 Dmitry S. Kravtsov
2011-01-29 23:13 ` Jonathan Nieder
2011-02-01 13:51   ` Jakub Narebski
2011-02-01 15:52     ` Nguyen Thai Ngoc Duy
2011-02-01 16:33       ` Shawn Pearce
2011-02-01 16:27     ` Shawn Pearce
2011-02-01 17:05       ` Nguyen Thai Ngoc Duy
2011-02-01 21:27         ` Junio C Hamano
2011-02-01 21:44         ` Nicolas Pitre
2011-02-01 17:11       ` Nguyen Thai Ngoc Duy
2011-02-01 17:34         ` Shawn Pearce
2011-02-01 21:51           ` Nicolas Pitre
2011-02-02  0:26             ` Shawn Pearce
2011-02-02  2:11               ` Nicolas Pitre
2011-02-02  2:23                 ` david
2011-02-03 14:38             ` Geert Bosch
2011-02-03 17:39               ` Narrow clone (Re: features from GitSurvey 2010) Jonathan Nieder
2011-02-03 21:23                 ` Geert Bosch
2011-02-03 21:33                   ` Jonathan Nieder
2011-02-03 21:38                   ` Jonathan Nieder
2011-02-03 21:33               ` Features from GitSurvey 2010 Nicolas Pitre
2011-02-01 17:28     ` Tracking empty directories Jonathan Nieder
2011-02-01 17:54       ` Nguyen Thai Ngoc Duy
2011-02-01 18:15         ` Ilari Liusvaara
2011-02-01 18:31           ` Jakub Narebski
2011-02-01 19:09             ` Ilari Liusvaara
2011-02-01 18:35         ` Jonathan Nieder
2011-02-01 19:03           ` Jakub Narebski
2011-02-02  3:54             ` Nguyen Thai Ngoc Duy
2011-02-02 12:31               ` Kevin P. Fleming [this message]
2011-02-01 21:36     ` Features from GitSurvey 2010 Nicolas Pitre
2011-02-01 22:50     ` big files in git was: " david
2011-02-03  6:25       ` Nicolas Pitre
2011-02-01 17:44   ` Matthieu Moy
2011-02-01 18:42     ` Jonathan Nieder
2011-02-01 20:23       ` Matthieu Moy

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=4D494EAA.2060803@digium.com \
    --to=kpfleming@digium.com \
    --cc=git@vger.kernel.org \
    --cc=idkravitz@gmail.com \
    --cc=jnareb@gmail.com \
    --cc=jrnieder@gmail.com \
    --cc=pclouds@gmail.com \
    --cc=spearce@spearce.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).