Many are lacking only because of the time it would take to find and merge them some are omitted by conscious decision to keep development focused and the high signal-to-noise ratio of the interface Not as many graphical niceties as some forks.64-bit Intel only, building for other targets is left as an exercise to the would-be user.But with a limited number of contributors, and to properly support Mac and iOS devs using the latest-and-greatest (even beta) environments there is an obvious need to reduce the support and maintenance load. Monetarily? No, GitX-dev will always be freely available. Improvements to the command-line gitx tool.Lower, more regular memory footprint due to porting to Objective-C Automatic Reference Counting. Significantly reduced ( and shrinking!) use of git command-line tool in favour of direct use of libgit2 and amework.Reliable in-app updates thanks to Sparkle.Notably better performance on large repositories.There are also a range of visible and under-the-hood changes to make GitX-dev a distinct improvement on other forks you may find. Clickable commit references in blame view.The awesome branch/remote/tag sidebar from GitX (L).GitX-dev includes a selection of improvements from around the GitX fork community. We want to make good version control an invisible, second-nature step of everyone working on a product. We consider it to be feature-complete for most git workflows, with only uncommon or potentially-destructive commands requiring git command-line interaction.Īs a collaboration tool for a diverse team trying to make other things we take feedback seriously from everyone involved in software production. GitX-dev is further specialised for software developers, and is used day-to-day in production environments. Good performance on large (200+ MB) repositories.Support for all parameters git rev-list has.Drag and drop files out of the tree view to copy them to your system.Preview any file in the tree in a text view or with QuickLook.Look at the complete tree of any revision.Search based on author or revision subject.See a nicely formatted diff of any revision.It has been maintained and enhanced with productivity and friendliness oriented changes, with effort focused on making a first-class, maintainable tool for today's active developers.įor the most up-to-date information, please see the change log for the latest bulid, or the live commit list.īuilding on the solid foundation of GitX, GitX-dev provides: Reload the terminal - source ~/.GitX-dev is a fork (variant) of GitX, a long-defunct GUI for the git version-control system.It may be save with a name git.bak and delete the original file If yes, then open the directory and locate the was a binary executable.Run which git and observe if Git is still linked to /usr/bin/git.added /usr/local/Cellar/git/2.4.0/bin to path, reload Bash, and run gitk.Updates - If you do not have homebrew on your Mac, get it installed first. Find all occurrences of lime in the file & replace them with "#99FF00". Locate gitk executable (typically at /usr/local/bin/gitk), take a backup & open it in a text editor. This step is relevant if you're using OS X v10.11 (El Capitan) or higher, and you run into an unknown color name “lime” error. If you don't have a bash_profile file and want to learn how to create one, then click here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |