From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
To: Heiko Voigt <hvoigt@hvoigt.net>
Cc: msysGit Mailinglist <msysgit@googlegroups.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: Re: git gui create desktop icon currently does not work
Date: Thu, 25 Feb 2010 08:53:57 +0100 [thread overview]
Message-ID: <cb7bb73a1002242353h739786bdlb2c57df3438f5b7f@mail.gmail.com> (raw)
In-Reply-To: <20100223230238.GD11271@book.hvoigt.net>
On Wed, Feb 24, 2010 at 12:02 AM, Heiko Voigt <hvoigt@hvoigt.net> wrote:
> On Tue, Feb 23, 2010 at 11:54:40PM +0100, Giuseppe Bilotta wrote:
>> On Tue, Feb 23, 2010 at 11:49 PM, Heiko Voigt <hvoigt@hvoigt.net> wrote:
> [...]
>> > From 5c22c39d530ffb308826629d974048d30cd32e53 Mon Sep 17 00:00:00 2001
>> > From: Heiko Voigt <hvoigt@hvoigt.net>
>> > Date: Tue, 23 Feb 2010 10:40:14 +0100
>> > Subject: [PATCH 1/2] git-gui: fix usage of _gitworktree when creating shortcut for windows
>> >
>> > Signed-off-by: Heiko Voigt <heiko.voigt@mahr.de>
>> > ---
>> > git-gui/lib/shortcut.tcl | 2 +-
>> > 1 files changed, 1 insertions(+), 1 deletions(-)
>> >
>> > diff --git a/git-gui/lib/shortcut.tcl b/git-gui/lib/shortcut.tcl
>> > index 79c1888..8cad0e2 100644
>> > --- a/git-gui/lib/shortcut.tcl
>> > +++ b/git-gui/lib/shortcut.tcl
>> > @@ -16,7 +16,7 @@ proc do_windows_shortcut {} {
>> > [info nameofexecutable] \
>> > [file normalize $::argv0] \
>> > ] \
>> > - [file normalize [$_gitworktree]]
>> > + [file normalize $_gitworktree]
>> > } err]} {
>> > error_popup [strcat [mc "Cannot write shortcut:"] "\n\n$err"]
>> > }
>>
>> Ouch. Yes, I think your patch is obviously correct.
>>
>> (I'll go sit in a corner with my 'TCL Dunce' cap on for a while ...)
>
> No problem obviously nobody else saw this, but please test your patches
> in the future. That could have avoided this one.
You're right, although finding a Windows installation on which to test
git is nontrivial for me. (I did mention this particular part was
untested when I submitted it.)
> One thing which is missing from my patch is the cygwin part which, as I
> saw from your original patch, has the same problem.
Also, I'm wondering: does the Windows part actually need a [file
nativename $_gitworktree], or is this automatically handled by the
shortcut creation code?
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2010-02-25 7:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 22:49 git gui create desktop icon currently does not work Heiko Voigt
2010-02-23 22:54 ` Giuseppe Bilotta
2010-02-23 23:02 ` Heiko Voigt
2010-02-25 7:53 ` Giuseppe Bilotta [this message]
2010-02-27 20:41 ` Heiko Voigt
2010-02-27 20:45 ` [PATCH 1/3] git-gui: fix usage of _gitworktree when creating shortcut for windows Heiko Voigt
2010-02-27 20:47 ` [PATCH 2/3] git-gui: fix PATH environment for mingw development environment Heiko Voigt
2010-02-28 0:57 ` [msysGit] " Pat Thoyts
2010-02-28 12:46 ` Heiko Voigt
2010-02-27 20:48 ` [PATCH 3/3] git-gui: fix shortcut creation on cygwin Heiko Voigt
2010-03-08 11:17 ` [PATCH 1/3] git-gui: fix usage of _gitworktree when creating shortcut for windows Johannes Schindelin
2010-02-27 22:09 ` Re: Re: git gui create desktop icon currently does not work Giuseppe Bilotta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cb7bb73a1002242353h739786bdlb2c57df3438f5b7f@mail.gmail.com \
--to=giuseppe.bilotta@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=hvoigt@hvoigt.net \
--cc=msysgit@googlegroups.com \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).