From: Junio C Hamano <junkio@cox.net>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Carl Baldwin <cnb@fc.hp.com>, git@vger.kernel.org
Subject: Re: [RFC] Removing deleted files after checkout
Date: Tue, 23 Aug 2005 17:02:00 -0700 [thread overview]
Message-ID: <7vu0hgmccn.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0508231830280.23242@iabervon.org> (Daniel Barkalow's message of "Tue, 23 Aug 2005 18:34:30 -0400 (EDT)")
Daniel Barkalow <barkalow@iabervon.org> writes:
> I think that git-read-tree -u ought to remove a directory if it removes
> the last file (or directory) in it.
I concur and do not have much objections to a patch that would
do so.
prev parent reply other threads:[~2005-08-24 0:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 16:21 [RFC] Removing deleted files after checkout Carl Baldwin
2005-08-23 19:43 ` Daniel Barkalow
2005-08-23 20:50 ` Carl Baldwin
2005-08-23 21:27 ` Daniel Barkalow
2005-08-23 21:40 ` Carl Baldwin
2005-08-23 22:12 ` Daniel Barkalow
2005-08-23 21:54 ` Junio C Hamano
2005-08-23 22:21 ` Carl Baldwin
2005-08-23 22:34 ` Daniel Barkalow
2005-08-24 0:02 ` Junio C Hamano [this message]
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=7vu0hgmccn.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=barkalow@iabervon.org \
--cc=cnb@fc.hp.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).