git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jim MacBaine" <jmacbaine@gmail.com>
To: git@vger.kernel.org
Subject: cg-status and empty directories
Date: Mon, 27 Feb 2006 15:43:32 +0100	[thread overview]
Message-ID: <3afbacad0602270643k9fdd255w8f3769ad77c54e65@mail.gmail.com> (raw)

Hello,

Short story: Recently I noticed a change in the way, cogito handles
empty directories.  Before, empty directories have been silently
ignored. Now cg-status always lists the status of empty directories as
unknown, but it still refuses to add them. If there is a good reason
for this behaviour, can someone enlighten me?

Long story: I'm using cogito to track and distribute changes on the
/etc directories of a few (almost) identical machines.  Whenever I
install a package which modifies somthing in /etc, I commit those
changes.  But with cg-status reporting all the empty directories as
"unknown", my brain needs a long time to parse the list and find the
really unknown files which shall be put under version control.

Many packages put empty directories under /etc, and although only a
few of those directories are actually needed, the automatic removal of
those packages will fail if I remove the empty directories manually.  
Equally, the removal will fail, if I put a .placeholder file into
those direrectories and cg-add it.  Is there a simple way out?

Regards,
Jim

             reply	other threads:[~2006-02-27 14:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-27 14:43 Jim MacBaine [this message]
2006-02-27 15:22 ` cg-status and empty directories Andreas Ericsson
2006-02-27 18:39   ` Jim MacBaine
2006-03-26 14:25 ` [PATCH] Do not ever list empty directories in git-ls-files --others Petr Baudis
2006-03-26 14:59   ` [PATCH] Optionally do not " Petr Baudis
2006-03-26 21:32     ` Junio C Hamano
2006-03-26 21:37 ` cg-status and empty directories Petr Baudis

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=3afbacad0602270643k9fdd255w8f3769ad77c54e65@mail.gmail.com \
    --to=jmacbaine@gmail.com \
    --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).