From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: "Németh Márton" <nm127@freemail.hu>,
"V4L Mailing List" <linux-media@vger.kernel.org>
Subject: Re: git problem with uvcvideo
Date: Wed, 03 Feb 2010 14:19:18 -0200 [thread overview]
Message-ID: <4B69A206.2010304@redhat.com> (raw)
In-Reply-To: <4B5DF582.1080602@infradead.org>
Mauro Carvalho Chehab wrote:
> However, the html URL is currently broken:
>
> $ rm -rf uvcvideo/ && git clone -l --bare /git/linux-2.6.git/ uvcvideo && cd uvcvideo && git remote add uvcvideo http://linuxtv.org/git/pinchartl/uvcvideo.git && git remote update
> Initialized empty Git repository in /home/mchehab/tst/uvcvideo/uvcvideo/
> Updating uvcvideo
>
> Probably, the rewrite rules at the server for http are incomplete. I'll see if I can fix it.
Fixed.
Basically, for http: to work, the http server shouldn't call gitweb handler. So, a different URL
is needed for gitweb and for git pull... Also, I needed to enable an post-update hook to be sure that
some references are generated after a push.
I've updated the gitweb to display the proper URL's.
Basically, the gitweb interface is available via http://git.linuxtv.org.
So, for uvcvideo, we have:
http://git.linuxtv.org/pinchartl/uvcvideo.git (gitweb interface, for browsing)
For adding a remote to that tree, you should use either:
git remote add uvcvideo git://linuxtv.org/pinchartl/uvcvideo.git
or
git remote add uvcvideo http://linuxtv.org/git/pinchartl/uvcvideo.git
Both is working, but using the git: URL is better. The http: URL should be used only when
behind a firewall that blocks the git port (tcp port 9418).
--
Cheers,
Mauro
next prev parent reply other threads:[~2010-02-03 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 21:31 git problem with uvcvideo Németh Márton
2010-01-25 18:07 ` Laurent Pinchart
2010-01-25 19:48 ` Mauro Carvalho Chehab
2010-02-03 16:19 ` Mauro Carvalho Chehab [this message]
2010-01-25 19:53 ` Németh Márton
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=4B69A206.2010304@redhat.com \
--to=mchehab@redhat.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=nm127@freemail.hu \
/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