From: Matthias Lederhofer <matled@gmx.net>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [RFH] straightening out "read-tree -m"
Date: Sun, 18 Mar 2007 13:18:10 +0100 [thread overview]
Message-ID: <20070318121810.GA17807@moooo.ath.cx> (raw)
In-Reply-To: <7vtzwjnhcb.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
> A B Outcome
> ----------------------------------------------------------------
> D D No problem.
>
> D F This should result in refusal when there are
> local modification to paths in "foo" directory,
> or there are untracked (but unignored) paths in
> "foo/".
What about ignored configuration files like config.mak?
Let's say there is an ignored configuration file in a subdirectory.
If this subdirectory is replaced by a file git would delete the
ignored configuration file?
next prev parent reply other threads:[~2007-03-18 12:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-18 7:25 [RFH] straightening out "read-tree -m" Junio C Hamano
2007-03-18 12:18 ` Matthias Lederhofer [this message]
2007-03-18 16:06 ` Brian Gernhardt
2007-03-18 20:23 ` Junio C Hamano
2007-03-18 23:20 ` Steven Grimm
2007-03-19 0:04 ` Junio C Hamano
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=20070318121810.GA17807@moooo.ath.cx \
--to=matled@gmx.net \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).