git-gui: Don't bother showing OS error message about hardlinks
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>
Shawn O. Pearce committed
Sep 24, 2007 at 08:26 UTC
40f86af01b061fbbd1e46d125280073322bf9f33
1 file changed
+1
-4
lib/choose_repository.tcl
+1
-4
@@ -496,10 +496,7 @@ method _do_clone2 {} {
496
[file join .git objects $i] \
497
[file join $objdir $i]
498
} err]} {
499
- info_popup [strcat \
500
- [mc "Hardlinks are unavailable. Falling back to copying."] \
501
- "\n" \
502
- $err]
499
+ info_popup [mc "Hardlinks are unavailable. Falling back to copying."]
500
set i [_copy_files $this $objdir $tolink]
501
} else {
502
set i [_link_files $this $objdir [lrange $tolink 1 end]]