<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git, branch gitgui-0.6.0</title>
<subtitle>Fork of git SCM with my patches.</subtitle>
<id>http://git.kilabit.info/git/atom?h=gitgui-0.6.0</id>
<link rel='self' href='http://git.kilabit.info/git/atom?h=gitgui-0.6.0'/>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/'/>
<updated>2007-02-12T22:45:21Z</updated>
<entry>
<title>git-gui: Change base version to 0.6.</title>
<updated>2007-02-12T22:45:21Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-02-12T22:45:21Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=fdf6cfc4266d1e88e74c09e9166fa0b5c9ad29cb'/>
<id>urn:sha1:fdf6cfc4266d1e88e74c09e9166fa0b5c9ad29cb</id>
<content type='text'>
This is the start of the 0.6 series of git-gui.  I'm calling it 0.6
(rather than any other value) as I already had a private tag on
one system based on 0.5, and that tag is quite a bit behind this
version.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;</content>
</entry>
<entry>
<title>git-gui: Guess our version accurately as a subproject.</title>
<updated>2007-02-12T22:05:10Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-02-12T22:05:10Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=07d082bf5b4bc353648ffd207fe2fbd9e57e4386'/>
<id>urn:sha1:07d082bf5b4bc353648ffd207fe2fbd9e57e4386</id>
<content type='text'>
When we are included as a subproject, such as how git.git carries
us, we want to retain our own version number and not the version
number assigned by git.git's own tags.  Consequently we need to
locate the correct tag which applies to our tree content and
its commit lineage.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;</content>
</entry>
<entry>
<title>git-gui: Handle gitgui tags in version gen.</title>
<updated>2007-02-12T21:38:29Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-02-12T21:38:29Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=6a6459bc8f1aa9e83b5b46f7c40454891bf5e92a'/>
<id>urn:sha1:6a6459bc8f1aa9e83b5b46f7c40454891bf5e92a</id>
<content type='text'>
I've decided to use gitgui-0.5 as the format for tags in the
git-gui repository.  The prefix of gitgui was chosen here to
make its namespace different from the namespace used by git
itself, allowing developers to pull both tag namespaces into
the same repository.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;</content>
</entry>
<entry>
<title>git-gui: Generate a version file on demand.</title>
<updated>2007-02-12T21:14:44Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-02-12T21:14:44Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=5d643cd3cebf5eab44d99c5c7e54a1dbef28cba6'/>
<id>urn:sha1:5d643cd3cebf5eab44d99c5c7e54a1dbef28cba6</id>
<content type='text'>
Because git-gui is being shipped as a subproject of the main
Git project and will often have a different lifecycle than
the main Git project, we should ship our own version number
in the release tarball rather than relying on the main Git
version file.

Git's master Makefile will invoke our own with the target
dist-version, asking us to save off our GITGUI_VERSION value
into our own version file, so that our GIT-VERSION-GEN script
can recover it at build time.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;</content>
</entry>
<entry>
<title>git-gui: Rename GIT_VERSION to GITGUI_VERSION.</title>
<updated>2007-02-12T21:12:04Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-02-12T21:12:04Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=7e81d4eead48c189d52406379150b09fd4096987'/>
<id>urn:sha1:7e81d4eead48c189d52406379150b09fd4096987</id>
<content type='text'>
Now that the decision has been made to treat git-gui as a
subproject, rather than merging it directly into git, we
should use a different substitution for our version value
to avoid any possible confusion.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;</content>
</entry>
<entry>
<title>git-gui: Allow gitexecdir, INSTALL to be set by the caller.</title>
<updated>2007-02-12T20:37:50Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-02-12T20:37:50Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=663e7cf81d970d8320147d4d58dce37aaebfb09b'/>
<id>urn:sha1:663e7cf81d970d8320147d4d58dce37aaebfb09b</id>
<content type='text'>
When used as a subproject within git.git our Makefile must honor
the gitexecdir which git.git's Makefile is passing down to us,
ensuring that we install our executables into the libexec chosen
by the end-user or packager.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;</content>
</entry>
<entry>
<title>git-gui: Stop deleting gitk preferences.</title>
<updated>2007-02-11T22:19:38Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-02-11T22:19:38Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=0960f7d6db89fa8418486cd088759e54dd51d54e'/>
<id>urn:sha1:0960f7d6db89fa8418486cd088759e54dd51d54e</id>
<content type='text'>
Now that git 1.5.0 and later contains a version of gitk that uses
correct geometry on Windows platforms, even if ~/.gitk exists, we
should not delete the user's ~/.gitk to work around the bug.  It
is downright mean to remove a user's preferences for another app.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;</content>
</entry>
<entry>
<title>git-gui: Focus into blame panels on Mac OS.</title>
<updated>2007-02-09T07:28:32Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-02-09T07:28:32Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=d585e782b0bfb11173028091cb11c8459766135c'/>
<id>urn:sha1:d585e782b0bfb11173028091cb11c8459766135c</id>
<content type='text'>
Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;</content>
</entry>
<entry>
<title>git-gui: Improve annotated file display.</title>
<updated>2007-02-09T06:59:38Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-02-09T06:59:38Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=486ef5270ce3162ee14634db825884cc466a32bf'/>
<id>urn:sha1:486ef5270ce3162ee14634db825884cc466a32bf</id>
<content type='text'>
Rather than trying to mark the background color of the line numbers
to show which lines have annotated data loaded, we now show a ruler
between the line numbers and the file data.  This ruler is just 1
character wide and its background color is set to grey to denote
which lines have annotation ready.  I had to make this change as I
kept loosing the annotation marker when a line was no longer colored
as part of the current selection.

We now color the lines blamed on the current commit in yellow, the
lines in the commit which came after (descendant) in red (hotter,
less tested) and the lines in the commit before (ancestor) in blue
(cooler, better tested).

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;</content>
</entry>
<entry>
<title>git-gui: Jump to the first annotation block as soon as its available.</title>
<updated>2007-02-09T03:41:51Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-02-09T03:41:51Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=1351ba13e599ef80bbfd9f9ef4ff22117418f030'/>
<id>urn:sha1:1351ba13e599ef80bbfd9f9ef4ff22117418f030</id>
<content type='text'>
To help clue users into the fact that annotation data arrives
incrementally, and that they should try to locate the region
they want while the tool is running, we jump to the first line
of the first annotation if the user has not already clicked on
a line they are interested in and if the window is still looking
at the very top of the file.

Since it takes a second (at least on my PowerBook) to even generate
the first annotation for git-gui.sh, the user should have plenty of
time to adjust the scrollbar or click on a line even before we get
that first annotation record in, which allows the user to bypass
our automatic jumping.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;</content>
</entry>
</feed>
