git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Leila Muhtasib <muhtasib@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-status: Show empty directories
Date: Sun, 10 Jun 2012 00:15:09 -0700	[thread overview]
Message-ID: <7vr4tnab9e.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1339270806-65013-1-git-send-email-muhtasib@gmail.com> (Leila Muhtasib's message of "Sat, 9 Jun 2012 15:40:06 -0400")

Leila Muhtasib <muhtasib@gmail.com> writes:

> git-status now lists empty directories under the untracked header. Before this
> modification, git status did not list empty directories. The header changed
> from 'Untracked files' to instead display 'Untracked files and directories'.
> A helpful reminder is also added after empty directories indicating they cannot
> be added/staged if they are empty. git status -u is unchanged, and will still
> only show untracked files just as before. As a result, no need for
> documentation change.

Please do not write a thick wall of text like this.  State the
problem you are trying to solve first, by describing the current
behaviour you want to highlight, and explain why you think the
current behaviour is bad.  Then describe how you propose to solve
that issue in a separate paragraph.

For example:

> git-status now lists empty directories under the untracked header. Before this
> modification, git status did not list empty directories.

The above is backwards.

	"git status" lists untracked files and directories full of
	untracked files, but does not list empty directories.  This
	is bad for such and such reasons.

Then describe your solution (which should be a short two sentence in
this case, because in the problem description you would have justified
adding "empty directories" section).

	Show empty directories to the "Untracked" section as well.
	Because an empty directory by definition does not have
	anything that the user could add, suggest the user to create
	a file to be committed and then add it.

Having said all that, I personally doubt this is a useful change.  I
may thought of adding a README file to a relatively new project that
does not yet have one while in shower but I haven't even created the
file in the working tree.  And I forget about it once I get to the
office.  Should the system remind me to create README and then add?
Your patch would not give me such a reminder once the top-level
directory is populated (because it is no longer empty).  Even if I
were planning to add Documentation/README instead, I would get such
a reminder only if the Documentation directory is empty. Once the
directory is populated, I wouldn't get "create README and then add".
Why should an empty directory so special?

  parent reply	other threads:[~2012-06-10  7:15 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 [this message]
2012-06-10 16:02   ` Leila
2012-06-10 18:12     ` konglu
2012-06-10 18:17       ` Leila
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=7vr4tnab9e.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=muhtasib@gmail.com \
    /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).