From: Catalin Marinas <catalin.marinas@gmail.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: Ben Clifford <benc@hawaga.org.uk>, git@vger.kernel.org
Subject: Re: latest stg/git commandline completions code
Date: Wed, 26 Oct 2005 12:34:22 +0100 [thread overview]
Message-ID: <b0943d9e0510260434y61dc5e50v@mail.gmail.com> (raw)
In-Reply-To: <200510251905.27768.blaisorblade@yahoo.it>
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.
> And let's leave Gentoo's emerge alone - I'd say imports can take up to a
> minute.
That's probably because it checks the status of the tree before
importing but this command wouldn't be used to generate the
completion.
--
Catalin
next prev parent reply other threads:[~2005-10-26 11:34 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 [this message]
2005-10-26 16:14 ` Blaisorblade
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=b0943d9e0510260434y61dc5e50v@mail.gmail.com \
--to=catalin.marinas@gmail.com \
--cc=benc@hawaga.org.uk \
--cc=blaisorblade@yahoo.it \
--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 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.