Feature #8633
Let contributors using Git know what they should do after the history rewrite
Status:
Resolved
Priority:
Normal
Assignee:
intrigeri
Category:
Infrastructure
Target version:
Start date:
2015-01-09
Due date:
% Done:
100%
Feature Branch:
Type of work:
Communicate
Starter:
Affected tool:
Deliverable for:
Description
Subtasks
Related issues
Blocked by Tails - |
Resolved | 2015-01-09 |
History
#1 Updated by intrigeri about 10 years ago
- blocked by
Feature #8632: Make sure various clones of our Git repository are up-to-date wrt. the rewrite added
#2 Updated by intrigeri about 10 years ago
- blocks deleted (
)Feature #8632: Make sure various clones of our Git repository are up-to-date wrt. the rewrite
#3 Updated by intrigeri about 10 years ago
- Parent task changed from
Feature #8617toFeature #6277
#4 Updated by intrigeri about 10 years ago
- blocked by
Feature #8632: Make sure various clones of our Git repository are up-to-date wrt. the rewrite added
#5 Updated by intrigeri about 10 years ago
- 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 about 10 years ago
Drafted, now need to test it in a more realistic context.
#7 Updated by intrigeri about 10 years ago
- % Done changed from 10 to 50
Doc tested, polished it a bit.
#8 Updated by intrigeri about 10 years ago
- Status changed from In Progress to Resolved
- % Done changed from 50 to 100
Email -dev@ and -l10n@ about it.
#9 Updated by BitingBird about 10 years ago
- Target version changed from Tails_1.3.2 to Tails_1.3.1