git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leila <muhtasib@gmail.com>
To: konglu@minatec.inpg.fr
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] git-status: Show empty directories
Date: Sun, 10 Jun 2012 14:17:02 -0400	[thread overview]
Message-ID: <CAA3EhHJzyR1pWaEeDp_+xv8LaaxmJfVXi17pNtwW3dAD+9sbFw@mail.gmail.com> (raw)
In-Reply-To: <20120610201256.Horde.dB69JnwdC4BP1OOoePf1xjA@webmail.minatec.grenoble-inp.fr>

On Sun, Jun 10, 2012 at 2:12 PM,  <konglu@minatec.inpg.fr> wrote:
>
> Leila <muhtasib@gmail.com> a écrit :
>
>
>> The question 'why are empty dirs special', is issue no 1, which I'm
>> also happy to discuss. The rule empty dirs can't be added in git is
>> unintuitive, as people use git to keep track of things - all things.
>> So it's not about an empty dir being special, it's about how people
>> use git to keep track of things. Now why might people want empty dirs
>> tracked? 1) People often setup dir structure in projects before adding
>> any code. They often want to save that state for themselves or to
>> share it with other team members.
>
>
> Yup, that kind of situation is not unusual. Thus, having a reminder by
> running 'git status' would help. But sharing empty dir with other team
> members is another issue, no ? Even with your implementation, the user
> won't be able to share empty directories.
>

Yes, there are two issues. I'm advocating for the reminder when
running 'git status'.

Sharing empty dirs with other team members is another issue. My
implementation does not handle this case.

Thanks,
Leila

  reply	other threads:[~2012-06-10 18:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-09 19:40 [PATCH] git-status: Show empty directories Leila Muhtasib
2012-06-09 20:13 ` konglu
2012-06-09 21:08   ` Leila
2012-06-09 21:14     ` Thomas Rast
2012-06-09 21:24       ` Leila
2012-06-09 21:47       ` konglu
2012-06-10  9:01         ` Thomas Rast
2012-06-10  9:46           ` konglu
2012-06-10 14:20             ` Leila
2012-06-11 15:08           ` Junio C Hamano
2012-06-10  7:15 ` Junio C Hamano
2012-06-10 16:02   ` Leila
2012-06-10 18:12     ` konglu
2012-06-10 18:17       ` Leila [this message]
2012-06-11 16:57     ` Junio C Hamano
2012-06-11 18:51       ` Leila
2012-06-11 19:00         ` Leila

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=CAA3EhHJzyR1pWaEeDp_+xv8LaaxmJfVXi17pNtwW3dAD+9sbFw@mail.gmail.com \
    --to=muhtasib@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=konglu@minatec.inpg.fr \
    /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).