<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git, branch gitgui-0.6.1</title>
<subtitle>Fork of git SCM with my patches.</subtitle>
<id>http://git.kilabit.info/git/atom?h=gitgui-0.6.1</id>
<link rel='self' href='http://git.kilabit.info/git/atom?h=gitgui-0.6.1'/>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/'/>
<updated>2007-02-21T06:33:59Z</updated>
<entry>
<title>git-gui: Don't crash in citool mode on initial commit.</title>
<updated>2007-02-21T06:33:59Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-02-21T06:33:59Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=981193786fc30b9ee73b9f223a75642b4ed455b9'/>
<id>urn:sha1:981193786fc30b9ee73b9f223a75642b4ed455b9</id>
<content type='text'>
Attempting to use `git citool` to create an initial commit caused
git-gui to crash with a Tcl error as it tried to add the newly
born branch to the non-existant branch menu.  Moving this code
to after the normal commit cleanup logic resolves the issue, as
we only have a branch menu if we are not in singlecommit mode.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;</content>
</entry>
<entry>
<title>git-gui: Remove TODO list.</title>
<updated>2007-02-21T06:29:05Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-02-21T06:29:05Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=7391b2e9991e138786a2ac049ce7f276f7abce40'/>
<id>urn:sha1:7391b2e9991e138786a2ac049ce7f276f7abce40</id>
<content type='text'>
I'm apparently not very good at keeping my own TODO file current.
I its also somewhat strange to keep the TODO list as part of the
software branch, as its meta-information that is not directly
related to the code.  I'm pulling the TODO list from git-gui and
moving it into a seperate branch.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;</content>
</entry>
<entry>
<title>git-gui: Include browser in our usage message.</title>
<updated>2007-02-21T06:24:57Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-02-21T06:24:57Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=c0f7a6c33da7ec875fb084c9d97e471cd3a14535'/>
<id>urn:sha1:c0f7a6c33da7ec875fb084c9d97e471cd3a14535</id>
<content type='text'>
Now that the 'browser' subcommand can be used to startup the tree
browser, it should be listed as a possible subcommand option in
our usage message.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;</content>
</entry>
<entry>
<title>git-gui: Change summary of git-gui.</title>
<updated>2007-02-21T05:11:02Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-02-19T02:08:04Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=019f42a4ffe66e35cfe32a18c3def0183e6a0129'/>
<id>urn:sha1:019f42a4ffe66e35cfe32a18c3def0183e6a0129</id>
<content type='text'>
Since git-gui does more than create commits, it is unfair to call
it "a commit creation tool".  Instead lets just call it a graphical
user interface.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;
</content>
</entry>
<entry>
<title>git-gui: Display all authors of git-gui.</title>
<updated>2007-02-21T05:11:01Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-02-19T02:06:48Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=871f4c97ad7e021d1a0a98c80c5da77fcf70e4af'/>
<id>urn:sha1:871f4c97ad7e021d1a0a98c80c5da77fcf70e4af</id>
<content type='text'>
Now that git-gui has been released to the public as part of Git 1.5.0
I am starting to see some work from other people beyond myself and
Paul.  Consequently the copyright for git-gui is not strictly the
two of us anymore, and these others deserve to have some credit
given to them.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;
</content>
</entry>
<entry>
<title>git-gui: Use mixed path for docs on Cygwin.</title>
<updated>2007-02-21T05:11:01Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-02-19T00:06:09Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=ee40599330e75d9266672ed5031b3f75764fea3d'/>
<id>urn:sha1:ee40599330e75d9266672ed5031b3f75764fea3d</id>
<content type='text'>
The Firefox browser requires that a URL use / to delimit directories.
This is instead of \, as \ gets escaped by the browser into its hex
escape code and then relative URLs are incorrectly resolved, Firefox
no longer sees the directories for what they are.  Since we are
handing the browser a true URL, we better use the standard / for
directories.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;
</content>
</entry>
<entry>
<title>git-gui: Correct crash when saving options in blame mode.</title>
<updated>2007-02-18T07:12:32Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-02-18T07:12:32Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=372ef954a15c321a1065bf7e764449ce7767277f'/>
<id>urn:sha1:372ef954a15c321a1065bf7e764449ce7767277f</id>
<content type='text'>
Martin Waitz noticed that git-gui crashed while saving the user's
options out if the application was started in blame mode.  This
was caused by the do_save_config procedure invoking reshow_diff
incase the number of context lines was modified by the user.
Because we bypassed main window UI setup to enter blame mode we
did not set many of the globals which were accessed by reshow_diff,
and reading unset variables is an error in Tcl.

Aside from moving the globals to be set earlier, I also modified
reshow_diff to not invoke clear_diff if there is no path currently
in the diff viewer.  This way reshow_diff does not crash when in
blame mode due to the $ui_diff command not being defined.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;</content>
</entry>
<entry>
<title>git-gui: Expose the browser as a subcommand.</title>
<updated>2007-02-16T05:24:03Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-02-16T05:24:03Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=b90d479255d3b47e3604493b58e271cb9cd8dccd'/>
<id>urn:sha1:b90d479255d3b47e3604493b58e271cb9cd8dccd</id>
<content type='text'>
Some users may find being able to browse around an arbitrary
branch to be handy, so we now expose our graphical browser
through `git gui browse &lt;committish&gt;`.

Yes, I'm being somewhat lazy and making the user give us
the name of the branch to browse.  They can always enter
HEAD.

Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;</content>
</entry>
<entry>
<title>git-gui: Create new branches from a tag.</title>
<updated>2007-02-15T06:34:40Z</updated>
<author>
<name>Martin Koegler</name>
<email>mkoegler@auto.tuwien.ac.at</email>
</author>
<published>2007-02-15T06:28:34Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=101e3ae7a6b041aa86505bfd3e8b901f1dc245c3'/>
<id>urn:sha1:101e3ae7a6b041aa86505bfd3e8b901f1dc245c3</id>
<content type='text'>
I'm missing the possibility to base a new branch on a tag.
The following adds a tag drop down to the new branch dialog.

Signed-off-by: Martin Koegler &lt;mkoegler@auto.tuwien.ac.at&gt;
Signed-off-by: Shawn O. Pearce &lt;spearce@spearce.org&gt;
</content>
</entry>
<entry>
<title>git-gui: Prefer version file over git-describe.</title>
<updated>2007-02-14T06:55:16Z</updated>
<author>
<name>Shawn O. Pearce</name>
<email>spearce@spearce.org</email>
</author>
<published>2007-02-14T06:55:16Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=26370f73c0e82bd67103e0868f84a44b536ff3fc'/>
<id>urn:sha1:26370f73c0e82bd67103e0868f84a44b536ff3fc</id>
<content type='text'>
Some distributions are using Git for part of their package
management system, but unpack Git's own source code for
delivery from the .tar.gz.  This means that when we walk
up the directory tree with git-describe to locate a Git
repository, the repository we find is for the distribution
and *not* for git-gui.  Consequently any tag we might find
there is bogus and does not apply to us.

In this case the version file should always exist and be
readable, as the packager is working from the released
.tar.gz sources.  So we should always favor the version
file over anything git-describe guess for us.

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