On Sun, Jul 17 2016, Christian Seiler wrote:
> That way, I always use SSH for alioth (and can then push
> without trouble, even if I first checked out a repository
> via debcheckout or similar), but the repositories can
> use the HTTPS URI instead for people without an alioth
> account.
That's
On Sun, Jul 17 2016, Jakub Wilk wrote:
> Are you sure it's about git:// vs https://?
Not anymore?!
> Shallow cloning has never worked for me reliably:
>
> $ git clone -v --depth=10 git://anonscm.debian.org/collab-maint/trend.git
> Cloning into 'trend'...
> Looking up anonscm.debian.org ... done.
On 07/17/2016 02:15 PM, Yuri D'Elia wrote:
> Regarding Lintian's informational warning about insecure git:// URIs in
> the Vcs-Git field:
>
> https://lintian.debian.org/tags/vcs-field-uses-insecure-uri.html
>
> I can switch easily from:
>
> git://anonscm.debian.org/collab-maint/trend.git
>
>
* Yuri D'Elia , 2016-07-17, 14:15:
Regarding Lintian's informational warning about insecure git:// URIs in
the Vcs-Git field:
https://lintian.debian.org/tags/vcs-field-uses-insecure-uri.html
I can switch easily from:
git://anonscm.debian.org/collab-maint/trend.git
to
Regarding Lintian's informational warning about insecure git:// URIs in
the Vcs-Git field:
https://lintian.debian.org/tags/vcs-field-uses-insecure-uri.html
I can switch easily from:
git://anonscm.debian.org/collab-maint/trend.git
to
https://anonscm.debian.org/git/collab-maint/trend.git
5 matches
Mail list logo