2 ms·
With a capable vcs you don't need a version number, hash or other id. These things are always fragile. Just add a comment saying that this is a rewrite of the
by weinzierl 11y ago
With a capable vcs you don't need a version number, hash or other id. These things are always fragile.
Just add a comment saying that this is a rewrite of the old part the code and document any intended functional differences. You can then search through the history for the first appearance of that specific comment. With git this is done with the pickaxe command.
- shawn-furyan 11y agoI think the issue here is that as nice as you might find your VCS tools when you write code, the code you are writing, particularly on code bases that are already old, may survive significantly longer than the current hot VCS. If the entire commit history gets squashed when the code base is ported over to a new VCS, then VCS history may not be robust enough to communicate with maintainers in the distant future (that is, potentially a decade or less from now given the typical half life of these sort of tools).
- kalleboo 11y agoI don't blame the devs 30 years ago for being cautious but now emacs has survived 5(?) VCS migrations with all the data intact, the tools are more mature now and it shouldn't be a worry anymore.