1
0
mirror of git://projects.qi-hardware.com/eda-tools.git synced 2024-07-01 03:22:01 +03:00
eda-tools/schhist
Werner Almesberger 31fe9c654b Added project sie-ceimtun. Plus some cleanup.
- schhist/Makefile (PHONY, all, update, sie-ceimtun-schhist,
  sie-ceimtun-schhist-upload), schhist/demo-index.html:  added project
  sie-ceimtun
- schhist/Makefile (all): also mention targets "update" and "upload-index"
- schhist/Makefile (atusd-schhist): SCHHIST_TITLE wasn't used
- schhist/demo-index.html: didn't like the <P>, changed it to <BR>
2010-09-25 05:27:50 -03:00
..
ppmdiff Initial commit of files moved over from ben-wpan. 2010-09-07 17:03:19 -03:00
demo-index.html Added project sie-ceimtun. Plus some cleanup. 2010-09-25 05:27:50 -03:00
gitenealogy Initial commit of files moved over from ben-wpan. 2010-09-07 17:03:19 -03:00
gitsch2ps gitsch2ps: added option -k to keep temporary clone of repository 2010-09-22 06:57:36 -03:00
gitwhoareyounow gitwhoareyounow: determine a file's final name in recorded future 2010-09-22 06:01:32 -03:00
Makefile Added project sie-ceimtun. Plus some cleanup. 2010-09-25 05:27:50 -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 Initial commit of files moved over from ben-wpan. 2010-09-07 17:03:19 -03:00
schhist2web schhist2web: users can now specify how names are ordered. 2010-09-22 10:14:38 -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 :-)