From: Yann Dirson <ydirson@linagora.com>
To: GIT ml <git@vger.kernel.org>
Subject: [BUG] Bad msysgit/egit interaction over dotfiles
Date: Tue, 8 Dec 2009 14:28:57 +0100 [thread overview]
Message-ID: <20091208132857.GB5425@linagora.com> (raw)
Some devs here started to use egit on windows, and since egit is not
complete yet, occasionally^Wregularly use msysgit for
rebase/stash/you-name-it.
This revealed a strange problem that took some time figuring out,
where eclipse refused to write to .classpath or .project, just saying
"could not write", while other apps had no problem editing the same
files.
In the end, the problem is that the dotfiles had the "hidden" bit set,
and that for some reason eclipse does not allow to write to hidden
files - and that the one (re)setting the "hidden" bit over and over
again is msysgit, whenever it checkouts such a dotfile - surely to
emulate the unix behaviour of hiding dotfiles by default.
I'm not sure who's at fault here - namely, I can't see any valid
reason for eclipse to refuse such writes, but I am not sure it is a
good reason for msysgit would set the hidden bit either. In either
case, even if only for the short term, I think msysgit should ensure
that this bit does not get set (possibly circumventing any magic msys
would do behind its back).
Best regards,
--
Yann
next reply other threads:[~2009-12-08 13:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 13:28 Yann Dirson [this message]
2009-12-08 13:34 ` [BUG] Bad msysgit/egit interaction over dotfiles Erik Faye-Lund
2009-12-08 13:42 ` Ferry Huberts
2009-12-08 14:23 ` Erik Faye-Lund
2009-12-08 14:37 ` Yann Dirson
2009-12-09 20:56 ` Marius Storm-Olsen
2009-12-10 8:35 ` Yann Dirson
2009-12-14 9:13 ` Erik Faye-Lund
2009-12-14 11:45 ` Johannes Schindelin
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=20091208132857.GB5425@linagora.com \
--to=ydirson@linagora.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