login
Search
"The latest feature release GIT 1.5.5 is available at the usual places," began Git maintainer Junio Hamano, adding "we kept this cycle just slightly over two months, as the previous 1.5.4 cycle was painfully tooooo long."
Git is a distributed version control system that was originally written by Linus Torvalds in April of 2005. It was written to be only a temporary replacement for BitKeeper, which Linus had been using to manage kernel source code since February of 2002. Junio Hamano took over maintainership of Git in July of 2005, and the tool has long since become quite popular outside of even Linux kernel development. Regarding the latest stable release, Junio highlighted some of the changes, including:
"Comes with git-gui 0.10.1; bunch of portability improvement patches coming from an effort to port to Solaris has been applied; 'git fetch' over the native git protocol used to make a connection to find out the set of current remote refs and another to actually download the pack data. We now use only one connection for these tasks; 'git commit' does not run lstat(2) more than necessary anymore; bash completion script (in contrib) are aware of more commands and options; a catch-all 'color.ui' configuration variable can be used to enable coloring of all color-capable commands, instead of individual ones such as 'color.status' and 'color.branch'; bash completion's prompt helper function can talk about operation in-progress (e.g. merge, rebase, etc.); 'git help' can use different backends to show manual pages and this can be configured using 'man.viewer' configuration; 'git gui' learned an auto-spell checking; 'git checkout' and 'git remote' are rewritten in C; two conflict hunks that are separated by a very short span of common lines are now coalesced into one larger hunk, to make the result easier to read."
Learning Git
I've been looking at using Git as a convenient way of storing some small projects of mine. I like the fact that the low-level "plumbing" commands make it easy to synthesize history after the fact--I have written a Python script that, given a set of versions of source files, builds them into a Git repository, using the file modification dates/times as commit dates/times.
Oh, one niggle, though--Git has a very strange way of dealing with time zones. And it records the time zone (in its own limited format) of each commit, which seems to me unnecessary--recording the UTC date/time should be enough.
Have you already submitted a
Have you already submitted a bugreport/feature request? This might be more fruitful.
Re: Learning Git
Oh, one niggle, though--Git has a very strange way of dealing with time zones. And it records the time zone (in its own limited format) of each commit, which seems to me unnecessary--recording the UTC date/time should be enough.
Git _records UTC date/time_ in the form of UNIX epoch. The time zone is purely informative, meant to convert data in UTC into localtime (e.g. to see which commits were made at deep night, local time ;-))