From: Junio C Hamano <junkio@cox.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Florent Thoumie <flz@xbsd.org>, git@vger.kernel.org
Subject: Re: Problem with git-push
Date: Wed, 01 Nov 2006 07:33:28 -0800 [thread overview]
Message-ID: <7v4ptj5ghj.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0611011205340.1670@wbgn013.biozentrum.uni-wuerzburg.de> (Johannes Schindelin's message of "Wed, 1 Nov 2006 12:12:43 +0100 (CET)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>> but more importantly, if the directory in question was created by
>> somebody else, I do not think this chmod() would succeed even if you are
>> in the same group as the owner (i.e. previous creator) of the directory.
>
> But if somebody else created it, it should already have the correct
> permissions in the first place (unless the user played around with them,
> which is not a pilot error, but a willfull pointing of the barrel in the
> general direction of your knee).
True; I think the yesterday's analysis is still incomplete. I
haven't reached the point where I can explain "is a directory".
If the directory was there and mkdir() failed (but we do not
check its return value), it would have set errno to EEXIST not
to EISDIR. There is something else going on.
>> [jc: I am CC'ing Johannes to blame him on commit 457f06d6;
>> git-pickaxe is turning out to be quite handy ;-)
>
> I am hating the tool already.
Well, we could rename it to "git credit" ;-).
next prev parent reply other threads:[~2006-11-01 15:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 14:48 Problem with git-push Florent Thoumie
2006-10-31 23:39 ` Junio C Hamano
2006-11-01 11:12 ` Johannes Schindelin
2006-11-01 15:33 ` Junio C Hamano [this message]
2006-11-01 21:43 ` Junio C Hamano
2006-11-01 22:54 ` Florent Thoumie
2006-11-01 22:11 ` Junio C Hamano
2006-11-02 9:42 ` Johannes Schindelin
2006-11-01 16:21 ` Junio C Hamano
2006-11-02 9:29 ` Johannes Schindelin
2006-11-03 2:40 ` Junio C Hamano
2006-11-01 19:57 ` Florent Thoumie
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=7v4ptj5ghj.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=flz@xbsd.org \
--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).