From: Bertrand Jacquin <beber.mailing@gmail.com>
To: Fredrik Kuivinen <freku045@student.liu.se>
Cc: Nick Hengeveld <nickh@reactrix.com>,
"Bertrand Jacquin (Beber)" <beber@guybrush.melee>,
git@vger.kernel.org
Subject: Re: git-http-push and hooks
Date: Tue, 7 Feb 2006 22:02:42 +0100 [thread overview]
Message-ID: <4fb292fa0602071302p551aca02j53d40e3f8e25ff8a@mail.gmail.com> (raw)
In-Reply-To: <20060207205709.GB7217@c165.ib.student.liu.se>
On 2/7/06, Fredrik Kuivinen <freku045@student.liu.se> wrote:
> On Tue, Feb 07, 2006 at 12:23:51PM -0800, Nick Hengeveld wrote:
> > On Tue, Feb 07, 2006 at 08:54:58PM +0100, Fredrik Kuivinen wrote:
> >
> > > I know basically nothing about DAV, but wouldn't it be possible to
> > > have a CGI-script which executes the hooks upon the client's request?
> >
> > It would, although if custom software can be run on the server you might
> > as well run the git daemon.
>
> You can't push to a git daemon, can you?
>
> Furthermore, if the user has a working http/DAV server installed it
> might be the case that she prefers to use that one instead of
> installing a new daemon.
Personaly is use http because at work i've a $$@#! proxy and allow dav
and nothing else.
Could you push over http/proxy with gitdaemon ? Isn't it just a read
only method ?
>
> - Fredrik
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Beber
#e.fr@freenode
next prev parent reply other threads:[~2006-02-07 21:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 20:52 git-http-push and hooks Bertrand Jacquin (Beber)
2006-02-06 23:22 ` Nick Hengeveld
2006-02-07 19:54 ` Fredrik Kuivinen
2006-02-07 20:23 ` Nick Hengeveld
2006-02-07 20:57 ` Fredrik Kuivinen
2006-02-07 21:02 ` Bertrand Jacquin [this message]
2006-02-07 23:41 ` Junio C Hamano
2006-02-07 21:17 ` Junio C Hamano
2006-02-07 22:45 ` Nick Hengeveld
2006-02-07 23:26 ` Junio C Hamano
2006-02-07 23:48 ` Nick Hengeveld
2006-02-07 20:51 ` Bertrand Jacquin
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=4fb292fa0602071302p551aca02j53d40e3f8e25ff8a@mail.gmail.com \
--to=beber.mailing@gmail.com \
--cc=beber@guybrush.melee \
--cc=freku045@student.liu.se \
--cc=git@vger.kernel.org \
--cc=nickh@reactrix.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).