From: Linus Torvalds <torvalds@linux-foundation.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "Craig L. Ching" <cching@mqsoftware.com>,
sverre@rabbelier.nl, Git Mailinglist <git@vger.kernel.org>
Subject: Re: Monotone workflow compared to Git workflow ( was RE: Git vs Monotone)
Date: Thu, 31 Jul 2008 20:02:51 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0807311956040.3277@nehalem.linux-foundation.org> (raw)
In-Reply-To: <20080801025024.GA18529@anvil.corenet.prv>
On Thu, 31 Jul 2008, Dmitry Torokhov wrote:
> > For example, for the kernel, I can literally rebuild my whole kernel
> > (which is just what I use on _that_ machine) in about 16 seconds. This is
> > _not_ using ccache or anything else - it's rebuilding the whole tree with
> > -j16.
>
> Is it after make mrproper (wow)?
Yeah. It's after doing
git clean -dqfx
make oldconfig
where I tend to use "git clean -dqfx" instead of "make mrproper" these
days.
Note that my "oldconfig" really only does the things I need, so this is
_not_ a "allmodconfig" or anything like that. That would take much longer.
It only has the drivers I use, and the stuff I actually need (it's not a
embedded kernel in any way, but it's definitely pared down config exactly
because I like being able to rebuild my kernels without wasting time on
thousands of drivers that I can't use anyway).
Other people can do the "does it compile?" testing. Not worth my time, I
feel ;)
> Because for me (and well, I dont have that beefy boxes as you do)
> swithing between "for-linus" and "next" that based off a revision in
> vicinity of 2.6.xx-rc1 and "work" which tracks the tip of your tree
> takes time to rebuild.
Well, the difference really is the beefy box. And the fact that I hate
modules, and I hate building stuff that I don't actually need.
I literally turn off CONFIG_MODULES entirely.
Linus
next prev parent reply other threads:[~2008-08-01 3:07 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 18:13 Git vs Monotone Sverre Rabbelier
2008-07-31 18:33 ` Stephen R. van den Berg
2008-07-31 18:52 ` Petr Baudis
2008-07-31 19:02 ` Jeff King
2008-07-31 19:11 ` Craig L. Ching
2008-07-31 19:19 ` Sverre Rabbelier
2008-07-31 20:32 ` Jeff King
2008-07-31 19:17 ` Linus Torvalds
2008-07-31 19:28 ` Craig L. Ching
2008-07-31 19:52 ` Linus Torvalds
2008-07-31 20:24 ` Junio C Hamano
2008-07-31 20:30 ` Linus Torvalds
2008-08-23 19:23 ` Felipe Contreras
2008-07-31 20:42 ` Blum, Robert
2008-08-10 22:15 ` Robin Rosenberg
2008-08-01 9:57 ` David Kastrup
2008-07-31 19:48 ` Monotone workflow compared to Git workflow ( was RE: Git vs Monotone) Craig L. Ching
2008-07-31 20:09 ` Linus Torvalds
2008-07-31 20:18 ` Shawn O. Pearce
2008-07-31 20:37 ` Craig L. Ching
2008-07-31 20:54 ` Björn Steinbrink
2008-07-31 21:10 ` Avery Pennarun
2008-07-31 21:13 ` Linus Torvalds
2008-07-31 21:43 ` Martin Langhoff
2008-07-31 21:40 ` Linus Torvalds
2008-08-01 2:50 ` Dmitry Torokhov
2008-08-01 3:02 ` Linus Torvalds [this message]
2008-08-01 3:59 ` Linus Torvalds
2008-07-31 20:57 ` Sean Estabrooks
2008-07-31 21:22 ` Theodore Tso
2008-07-31 19:24 ` Git vs Monotone Theodore Tso
2008-08-01 7:23 ` Sverre Rabbelier
2008-08-01 18:00 ` Daniel Barkalow
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=alpine.LFD.1.10.0807311956040.3277@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=cching@mqsoftware.com \
--cc=dmitry.torokhov@gmail.com \
--cc=git@vger.kernel.org \
--cc=sverre@rabbelier.nl \
/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;
as well as URLs for NNTP newsgroup(s).