Bug #11107

Apply transfer.fsckobjects true to our default Git config

Added by sajolida 2016-02-12 12:24:27 . Updated 2016-03-08 19:02:49 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2016-02-12
Due date:
% Done:

100%

Feature Branch:
Type of work:
Code
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

See:

Proposed but untested patch:

--- a/config/chroot_local-includes/etc/gitconfig
+++ b/config/chroot_local-includes/etc/gitconfig
@@ -1,2 +1,4 @@
 [color]
        ui = auto
+[transfer]
+       fsckObjects = true

Subtasks


History

#1 Updated by sajolida 2016-02-12 12:25:19

  • Assignee set to anonym
  • Target version set to Tails_2.2
  • QA Check set to Ready for QA

I’m not sure this qualifies as “Ready for QA” but I’ll let the RM decide on the priority of this.

#2 Updated by anonym 2016-02-24 18:05:47

  • Status changed from Confirmed to Fix committed
  • % Done changed from 0 to 100

Applied in changeset commit:73d7b643b3aca548703abe1fc144acd65b11f6af.

#3 Updated by anonym 2016-02-24 18:06:41

  • Assignee deleted (anonym)
  • QA Check changed from Ready for QA to Pass

I’ve been using this personally for a month, and it seems to work in Tails too. Applied, tanks!

#4 Updated by anonym 2016-03-08 19:02:49

  • Status changed from Fix committed to Resolved