From: Petr Baudis <pasky@suse.cz>
To: git@vger.kernel.org
Cc: Jesper Louis Andersen <jesper.louis.andersen@gmail.com>
Subject: Re: [CFH] Broken permissions in repo.or.cz repositories
Date: Fri, 11 Jul 2008 01:19:45 +0200 [thread overview]
Message-ID: <20080710231945.GD32184@machine.or.cz> (raw)
In-Reply-To: <20080710230058.GQ10151@machine.or.cz>
Hi,
On Fri, Jul 11, 2008 at 01:00:58AM +0200, Petr Baudis wrote:
> turns out current git has buggy handling of the sharedRepository
> config parameter, resulting in permission problems. Hopefully fixed.
sorry, this was not supposed to be cc'd to the mailing list in the
end, and is not CFH anymore. I'm trying to send a patch to the mailing
list now. :-)
--
Petr "Pasky" Baudis
The last good thing written in C++ was the Pachelbel Canon. -- J. Olson
prev parent reply other threads:[~2008-07-10 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56a0a2840807101218n7a280b67gfb3c579ada6b0e02@mail.gmail.com>
2008-07-10 23:00 ` [CFH] Broken permissions in repo.or.cz repositories Petr Baudis
2008-07-10 23:19 ` Petr Baudis [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=20080710231945.GD32184@machine.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=jesper.louis.andersen@gmail.com \
/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).