[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: git history tracking across renames (and emacs support)
From: |
Steinar Bang |
Subject: |
Re: git history tracking across renames (and emacs support) |
Date: |
Tue, 02 Jan 2018 23:04:02 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.2 (windows-nt) |
>>>>> Richard Stallman <address@hidden>:
>> If the result you pointed at is the case for all bzr moves converted to
>> git, then history tracking was lost at that point, and there isn't
>> really anything to do about it.
> Was the whole history of our repository lost at that time ???
No commits in the history of the repositor would have been lost.
But tracking the history of a file through renames would not be present.
(note that one wouldn't be worse off by this, than the regular state of
things in CVS)
- Re: git history tracking across renames (and emacs support), (continued)
- Re: git history tracking across renames (and emacs support), Paul Eggert, 2018/01/13
- Re: git history tracking across renames (and emacs support), Eli Zaretskii, 2018/01/13
- Re: git history tracking across renames (and emacs support), Paul Eggert, 2018/01/13
- Re: git history tracking across renames (and emacs support), Eli Zaretskii, 2018/01/13
- Re: git history tracking across renames (and emacs support), Eli Zaretskii, 2018/01/13
- Re: git history tracking across renames (and emacs support) (Was: The name gnus-cloud.el), Richard Stallman, 2018/01/15
- Re: git history tracking across renames (and emacs support) (Was: The name gnus-cloud.el), Richard Stallman, 2018/01/08
Re: git history tracking across renames (and emacs support),
Steinar Bang <=
Re: git history tracking across renames (and emacs support), Stefan Monnier, 2018/01/02