| 1 |
On Mon, Oct 6, 2014 at 10:48 AM, Michał Górny <mgorny@g.o> wrote: |
| 2 |
> I was thinking of prepending the old history via 'git replace' in |
| 3 |
> the gitweb repo to allow looking back. However, that idea has |
| 4 |
> the downside that users would be confused by having past commits in |
| 5 |
> gitweb yet not in clones. |
| 6 |
> |
| 7 |
> Kent improved my idea suggesting that we use a separate repo for that |
| 8 |
> 'complete history' view. That is, we would have three repos: |
| 9 |
> |
| 10 |
> 1. history.git -- with past CVS history up to conversion, |
| 11 |
> |
| 12 |
> 2. dev.git -- with history starting with conversion, |
| 13 |
> |
| 14 |
> 3. joined-history.git -- dev.git with 'git replace' for history.git, |
| 15 |
> that is the complete history including both pre- and post-conversion |
| 16 |
> commits. |
| 17 |
|
| 18 |
Can we do that without requiring the git replace stuff? E.g. have |
| 19 |
dev.git be a shallow clone of a joined-history.git? |
| 20 |
|
| 21 |
Cheers, |
| 22 |
|
| 23 |
Dirkjan |
Archives