lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 21 Sep 2006 18:25:54 -0400
From:	Sean <seanlkml@...patico.ca>
To:	David Lang <dlang@...italinsight.com>
Cc:	Dax Kelson <dax@...ulabs.com>,
	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>,
	Linux kernel <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...l.org>
Subject: Re: Smaller compressed kernel source tarballs?

On Thu, 21 Sep 2006 15:00:48 -0700 (PDT)
David Lang <dlang@...italinsight.com> wrote:

> yes,
>    however git users are people who plan on following every kernel version for a 
> while, tarball users are people who grab a copy of the kernel once in a while 
> (probably not every version). for the tarball users they would have to grab 
> multiple patches to get from the last thing that they have to whatever is 
> current. and frankly they may not (and probably should not) trust the last thing 
> that they have, as in many cases it's a distro patched kernel that may not be 
> compatable with the vanilla kernel.
>
> people who start downloading every revision should start useing git or patches, 
> but not everyone needs it.

Agreed, but for those people there isn't going to be much need (if any) to
worry about if the tar ball is in .gzip or .bzip2 or whatever then either.  And
that was the case that inspired the suggestion.
 
> also people could be behind a firewall that prevents git from working properly, 
> for them tarballs and patches are the right way of doing things.

I use git from behind a firewall everyday without a problem.  If you've seen
such a problem yourself, a bug report would hopefully lead to a solution.

Thanks,
Sean
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ