git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Jon Smirl <jonsmirl@gmail.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: monotone is slow
Date: Sat, 17 Feb 2007 01:17:38 -0500	[thread overview]
Message-ID: <20070217061738.GA27864@spearce.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0702162347430.22628@wbgn013.biozentrum.uni-wuerzburg.de>

Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> On Fri, 16 Feb 2007, Jon Smirl wrote:
> 
> > 45 CPU minutes to do a pull. About 2hrs real time.
> > 
> > jonsmirl@jonsmirl:~$ ps aux | grep mtn
> > jonsmirl  8382 80.5  4.4 131444 115204 pts/0   S+   14:54  45:44 mtn pull
> > 
> > And it worked, nothing was wrong. 1,500 revs pulled.
> > Let's convert the world to git.
> 
> But does it cook dinner?

No, Monotone doesn't.  As slow as it is...  and apparently one
could almost make a turkey while waiting for the merge.  Well,
a deep-fried turkey anyway.  :-)

But if you apply the following patch, Git will cook you dinner,
and faster than anyone else too!

diff --git a/git-merge.sh b/git-merge.sh
index 04a5eb0..00d083a 100755
--- a/git-merge.sh
+++ b/git-merge.sh
@@ -51,6 +51,7 @@ finish_up_to_date () {
 	'')
 		echo "$1" ;;
 	esac
+	echo "Also, your dinner is ready.  Most excellent."
 	dropsave
 }
 
@@ -95,6 +96,7 @@ finish () {
 		esac
 		;;
 	esac
+	echo "Git cooked you dinner! Go eat!"
 }
 
 merge_name () {


-- 
Shawn.

  reply	other threads:[~2007-02-17  6:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-16 21:20 monotone is slow Jon Smirl
2007-02-16 22:47 ` Johannes Schindelin
2007-02-17  6:17   ` Shawn O. Pearce [this message]
2007-02-17  6:19 ` Shawn O. Pearce

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=20070217061738.GA27864@spearce.org \
    --to=spearce@spearce.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jonsmirl@gmail.com \
    /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).