On Nov 11, 2017, at 5:14 AM, Richard Hipp <[email protected]> wrote:
>
> There is no way to track file merges in Fossil. Nor is there a way to
> track splits - when a single source code file is split into multiple
> smaller files because the original became too large.
Whenever I’ve had to do that, I add a line explaining the file’s provenance to
the module’s header comment:
Merged from foo.c and bar.c on 2017.11.14 by Warren Young
or
Extracted from foo.c on 2017.11.14 by Warren Young
Between that and the checkin comments near that date, I can backtrace merges
and splits manually.
What Fossil could backtrace automatically, and still doesn’t, are renames.
Change a file’s name and the “finfo” terminates at the rename point.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
