Skip to main content

Best SVN Linux GUI?

I've been searching for a good SVN front end for Linux to replace the command line check in. I want the capability to choose a subset of modified files from which to commit, rather than having to check in the entire directory structure each time by doing a "svn commit .". This feature comes standard with Tortoise, but Tortoise is Windows-only.

I first tried out RapidSVN. This is a GTK front end that stores bookmarks on working directories. However, it did not have what I wanted.

I also tried eSVN. This is a front end built on qt. Initially, I tried "File -> Open Working Directory..." and this hung. I ran the esvn binary from the directory containing my svn checkout and I was finally able to select a working directory. The GUI also allowed a selectable subset of files!

I understand there is a subversion plugin for Eclipse. I will give this a try on my Ubuntu box.

All of these attempts were made on a RHEL 5.0 machine.

Comments

  1. You might try KDESvn although I'm sure it is dependent on some of the KDE libraries.

    ReplyDelete

Post a Comment

Popular posts from this blog

C++ Development Environment

Trolling through some forums today, I found some great resources for C++, so I expanded on it and inserted some annotations. Categories are Integrated Development Environment (IDE), UML Interface, Team Collaboration, Coding Standards, Bug Tracking, Version Control, Unit Test Library, and Performance Testing. A bracket sits next to the resource which contains a W for Windows support, L for Linux, and M for Mac. A $ indicates that a standard version of the software will require a purchased license. IDE: Eclipse CDT ( eclipse.org ) [WLM] Visual SlickEdit ( slickedit.com ) [WLM$] UML: Eclipse MDT ( eclipse.org ) [WLM] Team Collaboration: Skype [WLM] Zoho [WLM] Sharepoint [W$] SourceForge [WLM] Coding Standards (Platform Agnostic): The Lockheed Martin Joint Strike Fighter C++ coding standards ( att.com ) The MISRA C++ coding standards [$] ( misra-cpp.org ) Bug Tracking: Bugzilla ( bugzilla.org ) [WLM] Unfuddle ( unfuddle.com ) [WLM] Version Control: mercurial subversion mercurial git cvs ...

The TL;DR guide to git

While in the past I've held a pretty high opinion to using mercurial for version control, the majority of version control these days seems to done in git.  Here were the commands I found most useful to get productive with git right away. # Clone a repository from an origin, i.e. my github MaskingUtils repository git clone git@github.com:caelumvox/masking-utils.git # Add a file after it's been updated to stage it for commit, or add a new file git add filename # Commit the file to local repo git commit # Push the file to the origin so the rest of the team can see it git push # List all locally tracked branches git branch git branch --list # Get a list of all branches from the remote git branch -r # Create branch locally git branch develop # Push the branch to the origin repository to make sure it is tracked there git push --set-upstream origin develop # Pulls latest from all local branches tracked from origin; won't pull non-tracked branches git pull --all # Fetch the branch ...

Software Design Principles - SOLID

The SOLID software design principles weren't called SOLID while I was in grad school, but the concepts were there in my Object Oriented Design course. They're worth mentioning here, primarily because I think once you start coding and become dangerous, it's one of the best ways to stay organized once you incorporate it into your daily coding routines, and it even changes your way of thinking for the better: https://en.wikipedia.org/wiki/SOLID