Free revision control system software for mac

Volume Control is a free Yahoo! widget that will allow you to easily control your volume! This light-weight Widget allows you to adjust and mute your computers volume with a simple mouse scroll or click of a button. You can even set the volume sensitivity.

System requirements:
-

Enhancements
- This initial version provides mouse-scroll volume adjustments, up and down volume buttons, a mute button, and in-volume click changes.

Stupid Button is a free Yahoo! widget that shows a big red button that says "that was stupid" when pressed.

System requirements:
-

Enhancements
- Initial Revision

MacMerc 1.0.1 provides a diversified and effective graphic wrapper for the Mercurial version control system. It is not intended to completely replace command line use of Mercurial, only to ease the most common Mercurial operations.

Bazaar is a distributed version control system available under the GPL that reduces barriers to participation in your project.
Bazaar is designed to support Mac OS, GNU/Linux, UNIX, Windows. In summary, Bazaar gives you fast, distributed revision control that "Just Works", supporting renames of directories and files smoothly.
Bazaar is designed to maximise the level of community participation in your project.
Bazaar branches can be published on any web server, and uploaded over sftp, ftp, or rsync. If you want the fastest possible network performance, there is a smart server.
Bazaar supports flexible work models: centralized like cvs or svn, commit offline, enforced code review when desired, and automatic regression testing.
Decentralized revision control systems give people the ability to collaborate more efficiently over the internet using the bazaar development model and have many other advantages.
When you use Bazaar, you can commit to your own local branches of your favourite free software projects without needing special permission.

Main features:
Good performance:
- Bazaar status in a tree of 5,000 files takes just 0.5 seconds, so almost every open source project can get the advanced features of Bazaar without slowing down its developers. Bazaar is robust in the face of radical tree restructuring, saving you time when it comes to merging from your community.
Safe with your data:
- There have not been any data loss bugs in a Bazaar release in the past two years. Bazaar has a huge test suite that ensures that new file formats can be tested automatically. The development process follows best practice with code review of all core and community code landings.
Friendly:
- Bazaar "Just Works" (which is why the Ubuntu team chose it for their project). Bazaar has a natural feel, you can publish your code on any web server or use a custom server for performance. Bazaar has perfect support for renaming files AND directories, which means you can unleash your community and merge efficiently even from contributors who are radically restructuring the tree.
Free:
- Bazaar is available under the GPL v2 or later.
Easy to integrate:
- Bazaar is designed as a Python API with a plugin system, so it is easy to embed in your tools and projects and easy to extend or integrate with existing infrastructure. Whether you are managing your development, or keeping track of configuration files, or building a new content management system, Bazaar is a great choice if you like to work in Python.

System requirements:
-

Enhancements
Compatibility Breaks:
- Display prompt on stderr (instead of stdout) when querying users so that the output of commands can be safely redirected. (Vincent Ladeuil, #376582)
New Features:
- A new repository format 2a has been added. This is a beta release of the the brisbane-core (aka group-compress) project. This format now suitable for wider testing by advanced users willing to deal with some bugs. We would appreciate test reports, either positive or negative. Format 2a is substantially smaller and faster for many operations on many trees. This format or an updated version will become the default in bzr 2.0.
- This is a rich-root format, so this repository format can be used with bzr-svn. Bazaar branches in previous non-rich-root formats can be converted (including by merge, push and pull) to format 2a, but not vice versa. We recommend upgrading previous development formats to 2a.
- Upgrading to this format can take considerable time because it expands and more concisely repacks the full history.
- If you use stacked branches, you must upgrade the stacked branches before the stacked-on branches. (See )
- --development7-rich-root is a new dev format, similar to --dev6 but using a Revision serializer using bencode rather than XML. (Jelmer Vernooij, John Arbash Meinel)
- mail_client=claws now supports --body (and message body hooks). Also uses configured from address. (Barry Warsaw)
Improvements:
- --development6-rich-root can now stack. (Modulo some smart-server bugs with stacking and non default formats.) (John Arbash Meinel, #373455)
- --development6-rich-root delays generating a delta index for the first object inserted into a group. This has a beneficial impact on bzr commit since each committed texts goes to its own group. For committing a 90MB file, it drops peak memory by about 200MB, and speeds up commit from 7s => 4s. (John Arbash Meinel)
- Numerous operations are now faster for huge projects, i.e. those with a large number of files and/or a large number of revisions, particularly when the latest development format is used. These operations (and improvements on OpenOffice.org) include: branch in a shared repository (2X faster), branch --no-tree (100X faster), diff (2X faster), tags (70X faster) (Ian Clatworthy)
- Pyrex version of bencode support. This provides optimized support for both encoding and decoding, and is now found at bzrlib.bencode. bzrlib.utils.bencode is now deprecated. (Alexander Belchenko, Jelmer Vernooij, John Arbash Meinel)
Bug Fixes:
- Bazaar can now pass attachment files to the mutt email client. (Edwin Grubbs, #384158)
- Better message in bzr add output suggesting using bzr ignored to see which files can also be added. (Jason Spashett, #76616)
- bzr pull -r 123 from a stacked branch on a smart server no longer fails. Also, the Branch.revision_history() API now works in the same situation. (Andrew Bennetts, #380314)
- bzr serve on Windows no longer displays a traceback simply because a TCP client disconnected. (Andrew Bennetts)
- Clarify the rules for locking and fallback repositories. Fix bugs in how RemoteRepository was handling fallbacks along with the _real_repository. (Andrew Bennetts, John Arbash Meinel, #375496)
- Fix a small bug with fetching revisions w/ ghosts into a new stacked branch. Not often triggered, because it required ghosts to be part of the fetched revisions, not in the stacked-on ancestry. (John Arbash Meinel)
- Fix status and commit to work with content filtered trees, addressing numerous bad bugs with line-ending support. (Ian Clatworthy, #362030)
- Fix problem of "directory not empty" when contending for a lock over sftp. (Martin Pool, #340352)
- Fix rule handling so that eol is optional, not mandatory. (Ian Clatworthy, #379370)
- Pushing a new stacked branch to a 1.15 smart server was broken due to a bug in the BzrDirFormat.initialize_ex smart verb. This is fixed in 1.16, but required changes to the network protocol, so the BzrDirFormat.initialize_ex verb has been removed and replaced with a corrected BzrDirFormat.initialize_ex_1.16 verb. 1.15 clients will still work with a 1.16 server as they will fallback to slower (and bug-free) methods. (Jonathan Lange, Robert Collins, Andrew Bennetts, #385132)
- Reconcile can now deal with text revisions that originated in revisions that are ghosts. (Jelmer Vernooij, #336749)
- Support cloning of branches with ghosts in the left hand side history. (Jelmer Vernooij, #248540)
- The bzr diff now catches OSError from osutils.rmtree and logs a helpful message to the trace file, unless the temp directory really was removed (which would be very strange). Since the diff operation has succeeded from the users perspective, no output is written to stderr or stdout. (Maritza Mendez, #363837)
- Translate errors received from a smart server in response to a BzrDirFormat.initialize or BzrDirFormat.initialize_ex request. This was causing tracebacks even for mundane errors like PermissionDenied. (Andrew Bennetts, #381329)
Documentation:
- Added directory structure and started translation of docs in Russian. (Alexey Shtokalo, Alexander Iljin, Alexander Belchenko, Dmitry Vasiliev, Volodymyr Kotulskyi)
API Changes:
- Added osutils.parent_directories(). (Ian Clatworthy)
- bzrlib.progress.ProgressBar, ChildProgress, DotsProgressBar, TTYProgressBar and child_progress are now deprecated; use ui_factory.nested_progress_bar instead. (Martin Pool)
- graph.StackedParentsProvider is now a public API, replacing graph._StackedParentsProvider. The api is now considered stable and ready for external users. (Gary van der Merwe)
- bzrlib.user_encoding is deprecated in favor of get_user_encoding. (Alexander Belchenko)
- TreeTransformBase no longer assumes that limbo is provided via disk. DiskTreeTransform now provides disk functionality. (Aaron Bentley)
Internals:
- Remove weave.py script for accessing internals of old weave-format repositories. (Martin Pool)
Testing:
- The number of cores is now correctly detected on OSX. (John Szakmeister)
- The number of cores is also detected on Solaris and win32. (Vincent Ladeuil)
- The number of cores is also detected on FreeBSD. (Matthew Fuller)