Git Queues (gq) is a series of bash scripts which add a Mercurial queues-like functionality and interface to git.
14 Nov 2006: Git Queues 0.10: The scripts are rather incomplete at the moment, but I’m hoping they’ll get to being very usable very soon.
(via LWN.net)
14 Nov 2006: Cogito 0.18.1: few minor new features and random bugfixes to the cogito-0.18 version. Nothing groundshattering.
(via LWN.net)
Several Git releases happened in recent weeks. I am catching up with the news.
Read more at LWN.net:
Quite a lot of changes during the last month;
[...]in the meantime here is primarily to fix git-svn correctness issues;
many minor fixes and documentation updates;
primarily to work around changes in the recent GNU diff output format. Also it contains irritation fix for “git diff” which now paginates its output by default;
qgit is a graphical git repositories viewer built on Qt libraries.
11 Nov 2006: qgit 1.5.3: This is mostly a bug fix release. Several issues has been fixed, also some crash bugs, so an update is
strongly suggested. To note is the new possibility to set the font used by patch and file content viewers.
(via LWN.net)
Keith Packard, a well-known X.org hacker, describes his reasons for choosing Git as a version control system for X.org.
X.org uses mostly centralized development style, and Git lets you continue working that way:
[...]it all depends on the conventions used within a project and individual developer style.At X.org, we migrated from CVS to Git and yet have retained our largely centralized development model. There are few people publishing alternate trees, and we grant direct repository access to the same set of developers who used to have CVS access.
According to Keith, Git also adds several useful features, thanks to its completely distributed origin, and to the format of its repository:
Git makes this supremely easy by allowing us to keep the ultra-secret new hardware changes in a private repository while still tracking the public repository. When we’re allowed to release the source code for the new hardware, we simply merge the private branch to the upstream master and push that to the public repository. All of the development history for the new hardware then becomes a part of the public source repository.
One interesting piece of information is repository size for large projects. It turns out that Git has very low overhead: The Mozilla CVS repository was 2.7GB, imported to Subversion it grew to 8.2GB. Under Git, it shrunk to 450MB. Given that a Mozilla checkout is around 350MB, it’s fairly nice to have the whole project history (from 1998) in only slightly more space.
(Similar numbers are reported in Tracking CVS repository with Git).
Read more at: “Repository Formats Matter” (title is a bit misleading) and “Tyrannical SCM selection”.
From: “Catalin Marinas” <catalin.marinas@gmail.com>
Date: Sat, 21 Oct 2006 16:08:31 +0100
Read more at LWN.net.
Christian Neukirchen describes a useful procedure for how to set up tracking of foreign CVS repository using Git, cvsup and cvsps 2.1. He uses the Ruby CVS repository as an example. The resulting GIT repository takes 29 megabytes and contains entire Ruby development history for eight years.
Read more at Tracking the Ruby CVS with Git.
P.S.: I had to install newer cvsps, and to edit the CVSROOT/config file, removing LockDir config option. Give git-cvsimport a -v flag to see what it is doing.
From: “Petr Baudis” <pasky+suse.cz>
Date: Fri, 29 Sep 2006 14:06:39 +0200
Hello,
I just released cogito-0.18 - new feature release of the Cogito
user-friendly Git user interface. The biggest highlights are
super-duper cg-log, tagging interface and cg-patch -m. Contrary to my
plan, this unfortunately does NOT contain three big things yet that are
missing but will be in cogito-0.19 (which should be already quite near
the ever-approaching version 1.0):
So, now for things that ARE part of 0.18: :-)
First, a simple README update is the only difference from 0.18rc2.
* INCOMPATIBLE: $COGITO_COLORS is renamed to $CG_COLORS
* INCOMPATIBLE: cg-log now by default hides merges, -M behaviour is reversed
* All kinds of very stale command aliases that were deprecated for eons were removed
* .git/author is deprecated (use .git/config to set it up)
* We now officially depend on 1.4.2 (we use git-*-fetch –stdin which makes fetching tags _MUCH_ faster)
* cg-log was reworked to support cg-log -d (show diffs inline), cg-log -S (pickaxe) and renames following (does not quite work, though; I decided not to fix it and wait for revisions.c in Git to support it since the perl script which takes care of this is quite a hack)
* cg-switch -l to stash your local changes when switching branches
* cg-commit –amend
* Tagging interface (cg-tag, cg-tag-ls, cg-tag-show) was greatly enhanced
* cg-patch -m for applying mailboxes
* cg-clone -l now sets up an alternate instead of symlinking the object db
* Support for cg-clone –reference
* cg-admin-setuprepo supports setting up repositories over SSH
* Support fetching over FTP
* Other cool stuff!
Happy hacking,
–
Petr “Pasky” Baudis
From: “Marco Costalba” <mcostalba@gmail.com>
Date: Sat, 30 Sep 2006 08:30:03 +0200
This is mostly a bug fix release.
Fixes are all over the place but most important are the fixes to code range filtering.
Code range filtering is when you select some text in file viewer and
want to view the list of revisions that modified that code range.
Download tarball from http://www.sourceforge.net/projects/qgit
or directly from git public repository
git://git.kernel.org/pub/scm/qgit/qgit.git
Please refer to http://digilander.libero.it/mcostalba/ for additional
information.
Marco
ChangeLog from 1.5.1