From: Morten Welinder <mwelinder@gmail•com>
To: Junio C Hamano <junkio@cox•net>
Cc: GIT Mailing List <git@vger•kernel.org>,
Linus Torvalds <torvalds@osdl•org>
Subject: Re: "git-checkout-cache -f -a" failure
Date: Mon, 9 May 2005 23:04:46 -0400 [thread overview]
Message-ID: <118833cc05050920045204db03@mail.gmail.com> (raw)
In-Reply-To: <7v64xru83t.fsf@assigned-by-dhcp.cox.net>
> Changing files vs directories _is_ a big change and happens
> rarely in practice; I think the current behaviour is
> justified---it makes the user take notice and the user _should_
> take notice.
File vs. directory was just the easiest way to demonstrate. In the presense
of symlinks I am not sure you will always get a warning. It'll be more of a
silent file-corrupting failure kind of thing. (Somewhat worse if yyy points
to /your/home/.ssh and zzz is "authorized_keys".)
Morten
next prev parent reply other threads:[~2005-05-10 2:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 18:25 "git-checkout-cache -f -a" failure Morten Welinder
2005-05-10 2:29 ` Junio C Hamano
2005-05-10 3:04 ` Morten Welinder [this message]
2005-05-10 22:57 ` Junio C Hamano
2005-05-10 23:03 ` Petr Baudis
2005-05-11 5:16 ` Junio C Hamano
2005-05-11 18:31 ` Morten Welinder
2005-05-11 21:37 ` Junio C Hamano
2005-05-11 22:12 ` Junio C Hamano
2005-05-11 22:40 ` Test suite Petr Baudis
2005-05-12 0:01 ` [PATCH] " Junio C Hamano
2005-05-12 19:29 ` Petr Baudis
2005-05-12 19:48 ` Junio C Hamano
2005-05-12 23:51 ` [PATCH] Fix git-diff-files for symlinks Junio C Hamano
2005-05-13 0:14 ` [PATCH 0/3] Core GIT fixes and additions Junio C Hamano
2005-05-12 0:02 ` [PATCH] checkout-cache fix Junio C Hamano
2005-05-12 19:38 ` Petr Baudis
2005-05-12 19:54 ` Junio C Hamano
2005-05-11 2:53 ` "git-checkout-cache -f -a" failure 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=118833cc05050920045204db03@mail.gmail.com \
--to=mwelinder@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=junkio@cox$(echo .)net \
--cc=torvalds@osdl$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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