From: me at fccagou.fr (Francois)
Subject: cgit and push method
Date: Wed, 26 Feb 2020 23:39:43 +0100 [thread overview]
Message-ID: <20200226223943.GB272214@l1nux> (raw)
First of all, congratulation for this software that gives an easy way to
access repos. I'm using around 5 hours ago and I have quickly found all
the customs options I was espected ... \o/ ....
Cgit is configured to allow cloning repos. I did not find information
for "push" management so I've tried a push but ... got a DAV lock error.
I am surprised at this behavior because it works if I use git-http-backend.
Looking the network traffic with tcpdump shows me that git does a PROPFIND
resquest when calling to cgit and only GET end POST when calling to
In the case of cgit and PROPFIND, cgit returns the html code of the
repo main page instead of the expected xml.
So I have some questions:
- does cgit allow push ?
- Is there a "best practice" to manage repos "backstage": create,
delete, give read/write acess
Thanks a lot in advance.
reply other threads:[~2020-02-26 22:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).