From: Adam Dinwoodie <adam@dinwoodie.org>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: Cygwin Git repos refusing push
Date: Sat, 8 Oct 2022 14:23:02 +0100 [thread overview]
Message-ID: <CA+kUOa=4PbGsZ1xj4F-6+L8tp4MaxRxjctknWESd_ijbd2S66A@mail.gmail.com> (raw)
In-Reply-To: <af8fb469-af38-2d1f-74e3-b115c4c669c4@dronecode.org.uk>
On Sat, 8 Oct 2022 at 14:12, Jon Turney wrote:
>
> On 04/10/2022 15:02, Adam Dinwoodie wrote:
> [...]
> >>
> >> I've adjusted the gitolite configuration so this should work again.
> >
> > Would it be possible to add some output to the hooks to provide a useful
> > explanation for what's going on? I think anything a hook prints to
> > stdout or stderr will be seen by the user in the `git push` output, and
> > something a bit more informative than "DENIED" would be nice!
>
> This is not totally straightforward, as this hook is part of, and
> managed by, gitolite.
>
> > It's not a big issue either way, but having a more informative output in
> > this case might have saved me a bit of time trying to ensure the problem
> > was genuinely on the server and not just that I was doing something
> > daft.
>
> Do you have a suggestion as to what else the hook should say?
Something to the effect of "This server does not permit pushing to any
branch other than 'master' or 'playground'" would have made it clearer
what was going on, at least for me. But as I say, if it's difficult to
do, it's not a big deal!
prev parent reply other threads:[~2022-10-08 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-04 7:55 Adam Dinwoodie
2022-10-04 12:28 ` Jon Turney
2022-10-04 14:02 ` Adam Dinwoodie
2022-10-08 13:12 ` Jon Turney
2022-10-08 13:23 ` Adam Dinwoodie [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='CA+kUOa=4PbGsZ1xj4F-6+L8tp4MaxRxjctknWESd_ijbd2S66A@mail.gmail.com' \
--to=adam@dinwoodie.org \
--cc=cygwin-apps@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).