git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: Ben Clifford <benc@hawaga.org.uk>, git@vger.kernel.org
Subject: Re: latest stg/git commandline completions code
Date: Wed, 26 Oct 2005 18:14:04 +0200	[thread overview]
Message-ID: <200510261814.04568.blaisorblade@yahoo.it> (raw)
In-Reply-To: <b0943d9e0510260434y61dc5e50v@mail.gmail.com>

On Wednesday 26 October 2005 13:34, Catalin Marinas wrote:
> On 25/10/05, Blaisorblade <blaisorblade@yahoo.it> wrote:
> > They _would_ behave like cat, except that Python is slow enough. Half a
> > second on a (almost) idle system means seconds and seconds on a busy
> > system, and it's pretty frequent that when I don't wait enough for an op.
> > to complete I get a traceback from the import statements, which haven't
> > been completed.

> That's a thing I should fix in StGIT - trapping the exception
> generated by SIGTERM and exiting silently.
Yep.

> > And let's leave Gentoo's emerge alone - I'd say imports can take up to a
With imports I mean Python import statement, in the case of the Gentoo 
"emerge" command (which is written in Python).

Not the import command (and checking the state of the tree can take tens of 
minutes, here - with a non-idle machine, though).
> > minute.
-- 
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade

	

	
		
___________________________________ 
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB 
http://mail.yahoo.it

  reply	other threads:[~2005-10-26 16:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.60.0510251222510.8565@mundungus.clifford.ac>
2005-10-25 14:42 ` latest stg/git commandline completions code Blaisorblade
2005-10-25 15:18   ` Catalin Marinas
2005-10-25 15:53     ` Blaisorblade
2005-10-25 16:24       ` Catalin Marinas
2005-10-25 17:05         ` Blaisorblade
2005-10-26 11:34           ` Catalin Marinas
2005-10-26 16:14             ` Blaisorblade [this message]
2005-11-08 10:16   ` Ben Clifford
2005-11-09 22:23     ` Petr Baudis
2005-11-10  1:59       ` Ben Clifford
2005-11-10  9:40         ` Petr Baudis
2005-11-16  3:35           ` Ben Clifford
2005-11-10  2:03       ` Ben Clifford
2005-11-10  6:57       ` Ben Clifford

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=200510261814.04568.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=benc@hawaga.org.uk \
    --cc=catalin.marinas@gmail.com \
    --cc=git@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;
as well as URLs for NNTP newsgroup(s).