1
0
mirror of git://projects.qi-hardware.com/eda-tools.git synced 2024-12-29 01:21:08 +02:00
eda-tools/schhist
Werner Almesberger f68e5a58b6 Option -D to keep temporary work trees for analysis/debugging.
- schhist/gitsch2ps: option -D to give _gitsch2ps a unique name, to copy
  the Postscript files instead of moving them, and to refrain from deleting
  _gitsch2ps
- schhist/schhist2web: option -D to refrain from deleting _gitsch2ps and
  to pass -D to gitsch2ps
2010-10-06 03:35:46 -03:00
..
ppmdiff Initial commit of files moved over from ben-wpan. 2010-09-07 17:03:19 -03:00
demo-index.html Added AVT2 to the Makefile and the demo index. 2010-10-03 23:31:35 -03:00
gitenealogy Initial commit of files moved over from ben-wpan. 2010-09-07 17:03:19 -03:00
gitsch2ps Option -D to keep temporary work trees for analysis/debugging. 2010-10-06 03:35:46 -03:00
gitwhoareyounow gitwhoareyounow: determine a file's final name in recorded future 2010-09-22 06:01:32 -03:00
Makefile Environment variable SCHHIST_ADDLIBS to force libraries to be present. 2010-10-04 03:04:35 -03:00
normalizeschps Initial commit of files moved over from ben-wpan. 2010-09-07 17:03:19 -03:00
README gitwhoareyounow: determine a file's final name in recorded future 2010-09-22 06:01:32 -03:00
sanitize-profile Environment variable SCHHIST_ADDLIBS to force libraries to be present. 2010-10-04 03:04:35 -03:00
sanitize-schem New script sanitize-schem to remove subsheets for which no file can be found. 2010-10-01 07:50:47 -03:00
schhist2web Option -D to keep temporary work trees for analysis/debugging. 2010-10-06 03:35:46 -03:00
schps2pdf Initial commit of files moved over from ben-wpan. 2010-09-07 17:03:19 -03:00
schps2ppm Initial commit of files moved over from ben-wpan. 2010-09-07 17:03:19 -03:00
subschname2file schhist/subschname2file: search a subsheet name in the top-level sheet and 2010-09-22 06:42:06 -03:00

gitwhoareyounow
---------------

gitwhoareyounow is used to find a single identity for files that have been
renamed in the history of a project.

E.g., if a file foo.c is created in revision 1 (assuming successive revisions
numbered 1, 2, etc.) and renamed to bar.c in revision 2, gitwhoareyounow
would then return the name bar.c for this file in any revision we consider.

gitwhoareyounow has to be given a repository in which the historical commit
has been checked out, and the name the file had in that commit.

Example:

$ git init
$ date >foo.c
# git add foo.c
# git commit -m "foo.c, rev 1"
$ git mv foo.c bar.c
$ git commit -m "foo.c renamed to bar.c, rev 2"
$ git checkout HEAD~1
$ ls
foo.c
$ gitwhoareyounow . foo.c
bar.c


Multiple files may use the same identity
- - - - - - - - - - - - - - - - - - - - 

E.g., if a file foo.c is created in revision 1, deleted in revision 3, and
then a new file named foo.c is created in revision 4, gitwhoareyounow would
call both of them foo.c


Multiple files sharing the same identity can conflict
- - - - - - - - - - - - - - - - - - - - - - - - - - -

E.g., taking the first example with foo.c renamed to bar.c in revision 3, if
a file bar.c existed in revision 1 but was deleted in revision 2,
gitwhoareyounow running on revision 1 would identify both the foo.c and the
bar.c as bar.c

gitwhoareyounow does not try to resolve such conflicts. This is already
complex enough as it is :-)