git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: How to Import a bitkeeper repo into git

From
PDPete/Piet Delaney <pete@bluelane.com>
Date
Oct 16, 2007, 00:41 UTC
Message-ID
<471408B8.8080509@bluelane.com>
In-Reply-To
<20071016000359.GT27899@spearce.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Shawn O. Pearce wrote:
Show 12 quoted lines
> Pete/Piet Delaney <pete@bluelane.com> wrote:
>> I imported the CVS repository to git and it worked great. Since all
>> of our other repository are in bitkeeper the management would like to
>> stick with CVS. With git apparently still being weak in the area of
>> supporting difftool on different version that seems somewhat reasonable
>> for the time being.
> ...
>> I was curious why the difftool paradigm hasn't been integrated into
>> the git GUIs. It's very comfortable and I think it has been used in
>> other source code control systems, for example Sun Microsystems.
> 
> What's difftool?  What's so great about it?

It's a side by side graphical diff. So instead of showing the difference like diff does it takes the output from diff and shows the originals with the diffs highlighted.

tkdiff is a good example that's easy to down load and see. So just imagine allowing git-gui to run tkdiff of revisions you select with the mouse.

Show 5 quoted lines
> 
> Forgive my ignorance but it has been many years since I last used
> BitKeeper and even when I did use it I didn't get into many of the
> features it offered.  Its entirely possible I never learned about
> difftool.

Try downloading tkdiff. There also a X implementation, I think it's xdiff.

Show 5 quoted lines
> 
> I've never found that I cannot get the information I need out of Git
> when I need it.  Actually I've found it to be the easiest VCS to get
> data out of, beating CVS, Perforce, BitKeeper, SVN, etc. hands down.
> Of course I also know Git better than I know those tools...

Try tkdiff and then tell me you don't find it easier to read that the straight output from diff.

- -piet
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHFAi4JICwm/rv3hoRAluCAJ9jFrA9G8aKQi1rtM2CSiNnmhlo4wCeJjk7 LONAM+lzvin021HAhQ8jKoE= =QsE/ -----END PGP SIGNATURE-----

Previous: Shawn O. PearceNext: David Brown
Message 6 of 39 in “How to Import a bitkeeper repo into git”
  1. free cycleJul 9, 2007
  2. VMiklosJul 9, 2007
  3. Linus TorvaldsJul 9, 2007
  4. Pete/Piet DelaneyOct 15, 2007
  5. Shawn O. PearceOct 16, 2007
  6. Pete/Piet DelaneyOct 16, 2007
  7. David BrownOct 16, 2007
  8. Linus TorvaldsOct 16, 2007
  9. David BrownOct 16, 2007
  10. Linus TorvaldsOct 16, 2007
  11. Pete/Piet DelaneyOct 16, 2007
  12. Marco CostalbaOct 16, 2007
  13. Pete/Piet DelaneyOct 16, 2007
  14. Marco CostalbaOct 16, 2007
  15. Andreas EricssonOct 16, 2007
  16. Marco CostalbaOct 17, 2007
  17. Andreas EricssonOct 17, 2007
  18. Pete/Piet DelaneyOct 17, 2007
  19. Marco CostalbaOct 17, 2007
  20. Pete/Piet DelaneyOct 17, 2007
  21. Pete/Piet DelaneyOct 17, 2007
  22. Marco CostalbaOct 17, 2007
  23. Robin RosenbergOct 17, 2007
  24. Marco CostalbaOct 17, 2007
  25. Robin RosenbergOct 18, 2007
  26. Pete/Piet DelaneyOct 18, 2007
  27. Johannes SchindelinOct 19, 2007
  28. Pete/Piet DelaneyOct 19, 2007
  29. Jeff KingOct 19, 2007
  30. Johannes SchindelinOct 19, 2007
  31. Jan WielemakerOct 19, 2007
  32. Pete/Piet DelaneyOct 19, 2007
  33. Jan WielemakerOct 19, 2007
  34. Andreas EricssonOct 19, 2007
  35. Pete/Piet DelaneyOct 19, 2007
  36. Andreas EricssonOct 19, 2007
  37. Jan HudecOct 16, 2007
  38. Linus TorvaldsOct 16, 2007
  39. Johannes SchindelinNov 6, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.