mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: david@lang.hm
Cc: 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 15:22:42 +0900	[thread overview]
Message-ID: <81e5df54-4987-40ba-9333-79665efda719@email.android.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1106061308590.25491@asgard.lang.hm>



david@lang.hm wrote:
>
>hmm, at this point would it make sense to have kernel.org generate the 
>tarball when it sees a new tag appear?

It's actually more of a "silly Linus scripts and workflow" issue. I have some trivial scripts that generate the tarballs and patches, and I'm just so used to running them at my own machine and then uploading them to the kernel.org machines.

I should just get used to doing the work directly on kernel.org, but normally it's faster and more convenient to just do it on my own machine. And I think this is the first time I've had an internet connection that was good enough to work with, but too flaky to actually upload things with.

I'll be home in another too many hours, will fix things up then..

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.

        Linus


  reply	other threads:[~2011-06-07  6:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-06  9:32 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 [this message]
2011-06-07  7:02         ` Tarkan Erimer
2011-06-07  7:21           ` Mike Galbraith
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=81e5df54-4987-40ba-9333-79665efda719@email.android.com \
    --to=torvalds@linux-foundation.org \
    --cc=alessandro.suardi@gmail.com \
    --cc=david@lang.hm \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®