Search Results for "big linux"

git-sizer computes various size metrics for a local Git repository, flagging those that might cause you problems or inconvenience. Is the repository too big overall? Ideally, Git repositories should be under 1 GiB, and (without special handling) they start to get unwieldy over 5 GiB. Big repositories take a long time to clone and repack, and take a lot of disk space. Avoid storing generated files (e.g., compiler output, JAR files) in Git. It would be better to regenerate them when necessary,...

This tool is intended to manage big files out of your VCS but in your workarea. It's like mercurial largefile extension but independend of any VCS. Instead of the big file itself only a list of filenames with their checksums (md5) are committed to the VCS. The BFM can check for missing or outdated bigfiles and downloads them from a server using CURL.

patchview is one addon to patchutils, with this tool you can view, in a simplified way,only the sub-patches, that you want, of one (big) patch file. You can split patches.To simplify this, it makes the enumeration of the files and you can choose b Code is now available on github : https://github.com/sergiomb2/patchutils

A local subversioning command line tool, written for those who find git troublesome and difficult to use for simple backups and snapshots of projects. The name is derived form being a small tool than git (which is really muscular), but skinny provide you easy to learn four commands and only used for local source management, commit log init restore ..thats it four commands no big deal. But its power lies in its simplicity formanaging Directory and Project States by making Snaposhots...

generate a GNU compliant ChangeLog file from the svn log messages using a very simple perl script. No big dependencies, no big libraries. Plain and simple.

A suite of CVS goodies written in perl for the harried Big Project Administrator.