Feature #8633

Let contributors using Git know what they should do after the history rewrite

Added by intrigeri 2015-01-09 14:21:29 . Updated 2015-03-22 12:09:29 .

Status:
Resolved
Priority:
Normal
Assignee:
intrigeri
Category:
Infrastructure
Target version:
Start date:
2015-01-09
Due date:
% Done:

100%

Starter:
Affected tool:
Deliverable for:

Description


Subtasks


Related issues

Blocked by Tails - Feature #8632: Make sure various clones of our Git repository are up-to-date wrt. the rewrite Resolved 2015-01-09

History

#1 Updated by intrigeri 2015-01-09 14:23:09

  • blocked by Feature #8632: Make sure various clones of our Git repository are up-to-date wrt. the rewrite added

#2 Updated by intrigeri 2015-01-09 14:29:45

  • blocks deleted (Feature #8632: Make sure various clones of our Git repository are up-to-date wrt. the rewrite)

#3 Updated by intrigeri 2015-01-09 14:29:58

#4 Updated by intrigeri 2015-01-09 14:39:35

  • blocked by Feature #8632: Make sure various clones of our Git repository are up-to-date wrt. the rewrite added

#5 Updated by intrigeri 2015-02-22 20:04:15

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 10
  • Blueprint set to https://tails.boum.org/blueprint/rewrite_Git_history/#post-rewrite-contributors-doc

#6 Updated by intrigeri 2015-02-22 20:07:01

Drafted, now need to test it in a more realistic context.

#7 Updated by intrigeri 2015-02-25 10:52:31

  • % Done changed from 10 to 50

Doc tested, polished it a bit.

#8 Updated by intrigeri 2015-02-25 17:59:09

  • Status changed from In Progress to Resolved
  • % Done changed from 50 to 100

Email -dev@ and -l10n@ about it.

#9 Updated by BitingBird 2015-03-22 12:09:29

  • Target version changed from Tails_1.3.2 to Tails_1.3.1