git-gui: Don't bother showing OS error message about hardlinks
authorShawn O. Pearce <spearce@spearce.org>
Mon, 24 Sep 2007 12:26:07 +0000 (08:26 -0400)
committerShawn O. Pearce <spearce@spearce.org>
Tue, 25 Sep 2007 01:48:38 +0000 (21:48 -0400)
If we failed to create our test hardlink for the first object
we need to link/copy then the only recourse we have is to make
a copy of the objects.  Users don't really need to know the OS
details about why the hardlink failed as its usually because
they are crossing filesystem boundaries.

Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
lib/choose_repository.tcl

index 5f2d12fd07c3217d068066f6b4b8714248e31d50..9074c1ba5ca1ede9321226caf37dbc57413fcf55 100644 (file)
@@ -496,10 +496,7 @@ method _do_clone2 {} {
                                        [file join .git objects $i] \
                                        [file join $objdir $i]
                        } err]} {
-                       info_popup [strcat \
-                               [mc "Hardlinks are unavailable.  Falling back to copying."] \
-                               "\n" \
-                               $err]
+                       info_popup [mc "Hardlinks are unavailable.  Falling back to copying."]
                        set i [_copy_files $this $objdir $tolink]
                } else {
                        set i [_link_files $this $objdir [lrange $tolink 1 end]]