people think it's a bug in CVS that makes it tag (and check in changes)
one file at a time. So most projects you'll ever see will use CVS
'as if' it was sane. In which case you'll find it very easy indeed to
people think it's a bug in CVS that makes it tag (and check in changes)
one file at a time. So most projects you'll ever see will use CVS
'as if' it was sane. In which case you'll find it very easy indeed to
First off: this is not a git tutorial. See
link:tutorial.html[Documentation/tutorial.txt] for how git
First off: this is not a git tutorial. See
link:tutorial.html[Documentation/tutorial.txt] for how git
"o-file.c", it would find the commit that changed the statement
when it was in "o-file.c".
"o-file.c", it would find the commit that changed the statement
when it was in "o-file.c".
enough to find copies, and it will miss the fact that a-file.c
was created by copying o-file.c unless o-file.c was somehow
enough to find copies, and it will miss the fact that a-file.c
was created by copying o-file.c unless o-file.c was somehow
You can use the --pickaxe-all flag in addition to the -S flag.
This causes the differences from all the files contained in
You can use the --pickaxe-all flag in addition to the -S flag.
This causes the differences from all the files contained in