| 1 |
On Thu, 18 Sep 2014 14:29:41 -0700 |
| 2 |
"W. Trevor King" <wking@×××××××.us> wrote: |
| 3 |
|
| 4 |
|
| 5 |
> |
| 6 |
> So Git works great, and GitHub's web UI doesn't support all of Git's |
| 7 |
> bells and whistles, so… switch to a different VCS? Personally, my |
| 8 |
> conclusion is “just use Git from the command line”. It's not like |
| 9 |
> you're abandoning long years of experience using CVSHub with some |
| 10 |
> miracle UI ;). |
| 11 |
|
| 12 |
--find-copies-harder |
| 13 |
For performance reasons, by default, -C option finds copies |
| 14 |
only if the original file of the copy was modified in the same |
| 15 |
changeset. This flag makes the command inspect unmodified files as |
| 16 |
candidates for the source of copy. This is a very expensive operation |
| 17 |
for large projects, so use it with caution. Giving more than one -C |
| 18 |
option has the same effect. |
| 19 |
|
| 20 |
P.S. As you see from description this option affects git performance. |
| 21 |
So, we probably can arrive at a conclusion that git itself isn't good |
| 22 |
at all for package management. Maybe there are better architectural |
| 23 |
decisions for that. |
Archives