git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Marco Costalba" <mcostalba@gmail.com>
To: pete@bluelane.com, piet.delaney@gmail.piet.net
Cc: "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: Wed, 17 Oct 2007 09:30:48 +0200	[thread overview]
Message-ID: <e5bfff550710170030y7778e96ax146acea7a0e57a67@mail.gmail.com> (raw)
In-Reply-To: <47159779.6010502@bluelane.com>

On 10/17/07, Pete/Piet Delaney <pete@bluelane.com> wrote:
>
> While I'm looking at the diffs for a file if I pull down External Diff
> it launches 'kcompare' but for a file with a large change it seems
> to be running extremely slow.

qgit does not intergarte Kompare functionality, it just prepares the
files and spawns a Kompare process.

So there's seem nothing qgit can do about Kompare speed. You can try
with different diff viewers, meld,...etc..


> for small files. Know of what can me done so that 'kcompare' works
> fast on large files; something like pointing it's tmp files to a
> not NFS partition.
>

Well temporary file sfor Kompare are created in the repository working
directory. If this is a problem for you you can save manually the
files corresponding to the two revisions you want to diff (open tree
view, select the file, right click to open context menu, save as...)

You need to repeat the above 'save as...' the first time selecting the
first revision you want to compare, then selecting the other revision
in main view, so that tree view is updated and you end-up saving the
correct files.

You can save the files where you want then run Kompare manually, at
least you test your assumption about slowness of NFS partition.

>
> Another problem I've noticed is that sometime while running git
> it seems to spend a large amount of time  switching from one
> change-set to the next; seems to be due to all of the tagged
> files.
>

If you can post a repository where this occurs and the step to
reproduce I can investigate further.

> > Another feature you asked, i.e. CTRL + right click to select a
> > revision (different from the parent) to diff against the current one
> > is also already implemented.
>
> It seems that while I'm in "Rev List" mode I can select the the
> two versions to compare a selected file with View->External diff...
>
> Now, if I pull down "View File" or go to the file context were
> you see the change-set for a file then I can't get the CTRL + right
> click to allow me to diff two revisions of the file.
>


Yes. This is true, is not supported this feature. Maybe could be added ;-)


>
> MY guess is that I should install a newer version of qgit,
> I'm using 1.5.3.
>

Please install 1.5.7, it has several bugs fixed.

> How difficult is it to upgrade to the Qt4. Can I just
> install it to /usr/local and not interfere with Qt3?

It does not interfere wuth Qt3 also if you install with urpmi,
directories are kept separated. I have installed both with no
problems.

> Last I recall messing with installing ethereal from src
> I needed a graphics lib and as I recall installing it in
> /usr/local/ confused some build crap. It would be interesting
> to try out your new qgit-2.0.
>

Qt4 is big and complex, I would really suggest avoid experimenting
with that library, stay safe and use urpmi.

> >
> > And of course the two above features can be integrated: you select two
> > random revisions and then call the external diff viewer to check at
> > the differences in the way you prefer.
>
> Right, but how do I do this from the file context?
>

In this case (and also in the above case of external viewer) you need
the magic wand ;-)

Select a file from tree view, go with the magic wand and you can do
everithing from main view.

>
> it seems to be pretty big. The date on 1.5.7 was very
> close to 2.0 so I thought they might be very close in
> functionality and you maintaining the same code for
> both the common Qt3 and the new Qt4 to make it easy
> for users to install.
>

Yes it is. qgit-1.5.7 should be very similar to qgit-2.0 regarding the
features you listed above.


Marco

  reply	other threads:[~2007-10-17  7:31 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 [this message]
2007-10-17 16:00                 ` Robin Rosenberg
2007-10-17 23:26                   ` Marco Costalba
2007-10-18 21:12                     ` Robin Rosenberg
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=e5bfff550710170030y7778e96ax146acea7a0e57a67@mail.gmail.com \
    --to=mcostalba@gmail.com \
    --cc=freecycler23@yahoo.com \
    --cc=git@vger.kernel.org \
    --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).