From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: "Marco Costalba" <mcostalba@gmail.com>
Cc: pete@bluelane.com, piet.delaney@gmail.piet.net,
"Linus Torvalds" <torvalds@linux-foundation.org>,
VMiklos <vmiklos@frugalware.org>,
"free cycle" <freecycler23@yahoo.com>,
git@vger.kernel.org, piet.delaney@gmail.com,
"Piet Delaney" <pdelaney@bluelane.com>
Subject: Re: How to Import a bitkeeper repo into git - Had a few questions on Qgit; I like the GUI.
Date: Thu, 18 Oct 2007 23:12:22 +0200 [thread overview]
Message-ID: <200710182312.23616.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <e5bfff550710171626h733228aw7a251746d2b43c63@mail.gmail.com>
torsdag 18 oktober 2007 skrev Marco Costalba:
> On 10/17/07, Robin Rosenberg <robin.rosenberg.lists@dewire.com> wrote:
> >
> > You could avoid the temporary files if you just pipe the diff to kompare. That
> > would require an option to tell qgit that the external viewer can read a git diff.
> >
> > At the time qgit 1.5 was written, kompare could not handle git diffs.
> >
>
> So does the other tools I have checked at that time.
>
> But I don't know if this fixes the problem of slowness reported. A
> little test Pete may do is just as I have written in the former email:
> try to save the big files that cause troubles where he prefers and run
> Kompare on them directly from the command line.
>
> Is kompare faster? If no probably the 'pipe' technique will not solve
> the problem and shrinks the applicability of the external diff
> launcher to tools that handle diffs directly.
kompare is pretty fast. Obviously not as fast as less.
"git diff HEAD HEAD~1000|kompare -" takes less than two seconds (hot cache)
on my machine. With small diffs it is almost instantaneous.
-- robin
next prev parent reply other threads:[~2007-10-18 21:10 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 16:57 How to Import a bitkeeper repo into git free cycle
2007-07-09 17:37 ` VMiklos
2007-07-09 17:51 ` Linus Torvalds
2007-10-15 23:39 ` Pete/Piet Delaney
2007-10-16 0:03 ` Shawn O. Pearce
2007-10-16 0:41 ` Pete/Piet Delaney
2007-10-16 1:13 ` David Brown
2007-10-16 0:45 ` Linus Torvalds
2007-10-16 1:12 ` David Brown
2007-10-16 1:22 ` Linus Torvalds
2007-10-16 3:45 ` Pete/Piet Delaney
2007-10-16 4:56 ` Marco Costalba
2007-10-16 6:05 ` Pete/Piet Delaney
2007-10-16 9:11 ` Marco Costalba
2007-10-16 17:05 ` Andreas Ericsson
2007-10-17 6:57 ` Marco Costalba
2007-10-17 15:50 ` Andreas Ericsson
2007-10-17 5:22 ` Pete/Piet Delaney
2007-10-17 7:14 ` Marco Costalba
2007-10-17 21:47 ` Pete/Piet Delaney
2007-10-17 5:02 ` How to Import a bitkeeper repo into git - Had a few questions on Qgit; I like the GUI Pete/Piet Delaney
2007-10-17 7:30 ` Marco Costalba
2007-10-17 16:00 ` Robin Rosenberg
2007-10-17 23:26 ` Marco Costalba
2007-10-18 21:12 ` Robin Rosenberg [this message]
2007-10-18 23:41 ` Qgit performance and maintain CVS environment with GIT repository Pete/Piet Delaney
2007-10-19 0:00 ` Johannes Schindelin
2007-10-19 0:22 ` Pete/Piet Delaney
2007-10-19 0:41 ` Jeff King
2007-10-19 0:50 ` Johannes Schindelin
2007-10-19 7:43 ` Jan Wielemaker
2007-10-19 8:58 ` Pete/Piet Delaney
2007-10-19 10:34 ` Jan Wielemaker
2007-10-19 7:14 ` Andreas Ericsson
2007-10-19 9:12 ` Pete/Piet Delaney
2007-10-19 9:52 ` Andreas Ericsson
2007-10-16 19:15 ` How to Import a bitkeeper repo into git Jan Hudec
2007-10-16 19:28 ` Linus Torvalds
[not found] ` <Pine.LNX.4.64.0710160100510.25221@racer.site>
[not found] ` <47140A5F.7000309@bluelane.com>
[not found] ` <Pine.LNX.4.64.0710160201220.25221@racer.site>
[not found] ` <4714130F.7030809@bluelane.com>
[not found] ` <Pine.LNX.4.64.0710160231040.25221@racer.site>
[not found] ` <47142AF3.1030405@bluelane.com>
[not found] ` <Pine.LNX.4.64.0710161154340.25221@racer.site>
[not found] ` <47303826.1000506@bluelane.com>
2007-11-06 10:51 ` git push problem - unpack unpacker exited with error code; ng refs/heads/rel2_branch n/a (unpacker error) Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200710182312.23616.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=freecycler23@yahoo.com \
--cc=git@vger.kernel.org \
--cc=mcostalba@gmail.com \
--cc=pdelaney@bluelane.com \
--cc=pete@bluelane.com \
--cc=piet.delaney@gmail.com \
--cc=piet.delaney@gmail.piet.net \
--cc=torvalds@linux-foundation.org \
--cc=vmiklos@frugalware.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).