From: Mike Galbraith <efault@gmx.de>
To: Tarkan Erimer <tarkan@turknetserver.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
david@lang.hm, Alessandro Suardi <alessandro.suardi@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.0-rc2
Date: Tue, 07 Jun 2011 09:21:46 +0200 [thread overview]
Message-ID: <1307431306.9428.16.camel@marge.simson.net> (raw)
In-Reply-To: <4DEDCCFF.10801@turknetserver.com>
On Tue, 2011-06-07 at 10:02 +0300, Tarkan Erimer wrote:
> On 06/07/2011 09:22 AM, Linus Torvalds wrote:
> > I suspect not a lot of people actually use the tarballs these days.
> > It's just much more convenient to get the tree with git.
>
>
> I always use tarballs instead of git. Because; I have several Linux
> boxes and just one time I download the kernel tarball then spreading it
> with scp to other Linux boxes easily. Otherwise, I have to prepare a
> tarball by myself to distribute it which is a time waste and
> unpractical. Also, getting the whole 700-800 MB of kernel tree with git
> is not very Internet bandwidth (Consider that in some ISPs and
> countries, Internet usage is limited by monthly quotas.) friendly.
My connection is crappy 400 kbit/s, but I use git easily. I set up a
git server, pull upstream daily, and all my boxen can then pull whatever
mainline/stable branch on local network. Initial clone hurts, but daily
pulls don't.
-Mike
next prev parent reply other threads:[~2011-06-07 7:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 9:32 Linux 3.0-rc2 Linus Torvalds
2011-06-06 10:27 ` Alessandro Suardi
2011-06-06 10:36 ` Alessandro Suardi
2011-06-06 11:25 ` Sven Joachim
2011-06-06 12:59 ` Linus Torvalds
2011-06-06 20:09 ` david
2011-06-07 6:22 ` Linus Torvalds
2011-06-07 7:02 ` Tarkan Erimer
2011-06-07 7:21 ` Mike Galbraith [this message]
2011-06-07 18:13 ` Tony Luck
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=1307431306.9428.16.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=alessandro.suardi@gmail.com \
--cc=david@lang.hm \
--cc=linux-kernel@vger.kernel.org \
--cc=tarkan@turknetserver.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.