All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
	"Dmitry S. Kravtsov" <idkravitz@gmail.com>,
	git@vger.kernel.org, Shawn Pearce <spearce@spearce.org>
Subject: Re: Tracking empty directories
Date: Tue, 1 Feb 2011 20:03:46 +0100	[thread overview]
Message-ID: <201102012003.50941.jnareb@gmail.com> (raw)
In-Reply-To: <20110201183508.GE3771@burratino>

Dnia wtorek 1. lutego 2011 19:35, Jonathan Nieder napisał:
> Nguyen Thai Ngoc Duy wrote:
>> On Wed, Feb 2, 2011 at 12:28 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> 
>>> I have ideas about how to resolve those tricky corner cases, but not
>>> about what the UI should look like.  How does one go about adding a
>>> directory?  Does it ever get implicitly removed?
>>
>> I suppose a special command for it is appropriate (git-keepdir?). Many
>> index-related commands are recursive by default and hard to change.
>>
>> Yes I think it should be automatically removed from index when a file
>> is added inside tracked directories. Removing those files will also
>> remove the containing directory though.
> 
> Okay, I'm convinced.  This fits a "worse is better" point of view
> nicely.
> 
> To add, one would use "git update-index --add".

Porcelain version could be "git add -N <directory>", don't you agree?

> 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?

-- 
Jakub Narebski
Poland

  reply	other threads:[~2011-02-01 19:09 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 [this message]
2011-02-02  3:54             ` Nguyen Thai Ngoc Duy
2011-02-02 12:31               ` Kevin P. Fleming
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=201102012003.50941.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=idkravitz@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 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.