From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: webmaster@kernel.org,
Linux Kernel list <linux-kernel@vger.kernel.org>,
hpa@kernel.org
Subject: Re: git pull through http / git
Date: Tue, 08 Jul 2008 09:22:11 +0200 [thread overview]
Message-ID: <487315A3.40302@atmel.com> (raw)
In-Reply-To: <alpine.LNX.1.10.0807071840470.8248@fbirervta.pbzchgretzou.qr>
Jan Engelhardt :
> On Monday 2008-07-07 18:15, Nicolas Ferre wrote:
>
>> Hi,
>>
>> I see differences when I use git to a git.kernel.org between the one I fetch
>> using http protocol and the one shown through the gitweb interface.
>>
>> I cloned (or git remote add) the mmc tree and my config shows this url :
>> url = http://www.kernel.org/pub/scm/linux/kernel/git/drzeus/mmc.git
>>
>> but I see updates in :
>> http://git.kernel.org/?p=linux/kernel/git/drzeus/mmc.git;a=summary
>> I cannot get.
>
> I don't think many care about http downloading, just because it is
> available as such.
> git:// and rsync:// are available though and should be usable even
> without the http info that needs to be constantly refreshed when one
> wants to use http....
If only I had the choice...
You certainly know why I am using http. This feature is very useful for
me and I was wondering why it was out of sync with the web interface.
Regards,
--
Nicolas Ferre
next prev parent reply other threads:[~2008-07-08 7:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 16:15 git pull through http / git Nicolas Ferre
2008-07-07 16:42 ` Jan Engelhardt
2008-07-07 18:03 ` H. Peter Anvin
2008-07-07 18:58 ` Jan Engelhardt
2008-07-08 3:31 ` H. Peter Anvin
2008-07-08 7:22 ` Nicolas Ferre [this message]
2008-07-08 7:34 ` J.H.
2008-07-08 14:27 ` Nicolas Ferre
2008-07-08 21:20 ` H. Peter Anvin
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=487315A3.40302@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=hpa@kernel.org \
--cc=jengelh@medozas.de \
--cc=linux-kernel@vger.kernel.org \
--cc=webmaster@kernel.org \
/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