Page MenuHomeDevCentral

Document properly woof history in Git history
Closed, ResolvedPublic

Description

Instead of an archiv folder, perhaps it would be useful to do successive commits, so we can track changes from one version to another.

Plan:

  • create an empty branch
  • commit in that branch different versions of woof under the name fileserv
  • git mv fileserv woof (*)
  • continue with woof versions (*)
  • merge allowing unrelated histories with the first commit of the woof repository

(*) we can also combine the first commit of woof after fileserv and the rename

That work is interesting enough to be offered upstream.

Related Objects

Event Timeline

dereckson triaged this task as Wishlist priority.Fri, Oct 18, 17:27
dereckson created this task.

Import script to create the commits:

1#!/bin/sh
2
3set -e
4
5BASE_DIR=$HOME/dev/nasqueron/wurf/archiv
6DATE="Fri Dec 31 23:59:59 2004 +0000"
7
8for file in $(grep fileserv /tmp/all.txt)
9do
10 cp $BASE_DIR/$file fileserv.py
11 git add fileserv.py
12 git commit -m "Import archive of $file" --author="Simon Budig <simon@budig.de>" --date="$DATE"
13done
14
15git mv fileserv.py woof.py
16
17for file in $(grep woof /tmp/all.txt)
18do
19 cp $BASE_DIR/$file woof.py
20 git add woof.py
21 git commit -m "Import archive of $file" --author="Simon Budig <simon@budig.de>" --date="$DATE"
22done

/tmp/all.txt was created with ls -1 > /tmp/all.txt.

Without a rebase and a change of the hashes, it's not possible to put commits BEFORE existing ones, so the best course of action is to put code in a specific branch, for example history.