1

Topic: GIT transfer of files from one in another with history saving

a question in a topic.
I  cannot understand it generally probably?
I do git mv - he writes any changes files are transferred. I do . I come in  - and there in the history of file changes - emptiness.
I come into idea, I include annotate - there history of all changes it is visible.
That for...? Where the history disappeared and how to transfer that history remained? Whence the idea takes the data about stories?

2

Re: GIT transfer of files from one in another with history saving

And yes specification... Through git log - follow all changes are visible. In  in the history of change are not visible.

3

Re: GIT transfer of files from one in another with history saving

Anybody  does not know - whether it is possible to transfer in  files with all history of change?

4

Re: GIT transfer of files from one in another with history saving

andreykaT wrote:

and yes specification... Through git log - follow all changes are visible. In  in the history of change are not visible.

How much I remember - follow is not supported .

5

Re: GIT transfer of files from one in another with history saving

Git commit works with . For  in  it is necessary git push

6

Re: GIT transfer of files from one in another with history saving

Not absolutely understood and here  and .  - we in change turnip deliver.  - we deliver  on remote .

7

Re: GIT transfer of files from one in another with history saving

OoCc wrote:

it is passed...
How much I remember - follow is not supported .

...On it is supported  truly? I am am tormented by a question - all  is saved and on a remote repository including, not only is local? The question can  but I will simply ask on  a case can  a broad gull -  reads changes whence-nibud from a local cache.

8

Re: GIT transfer of files from one in another with history saving

andreykaT wrote:

it is passed...
...On it is supported  truly? I am am tormented by a question - all  is saved and on a remote repository including, not only is local? The question can  but I will simply ask on  a case can  a broad gull -  reads changes whence-nibud from a local cache.

git log - follow reads from local . As soon as you made  your renaming and look history in  it it to you does not show since does not do - follow at  history of files.

9

Re: GIT transfer of files from one in another with history saving

It is clear. But after  if I do git follow - that everything is all right. I as see history.
I will tell more - if I move files BACK to the previous directory - the history again appears and in .

10

Re: GIT transfer of files from one in another with history saving

andreykaT wrote:

it is clear. But after  if I do git follow - that everything is all right. I as see history.
I will tell more - if I move files BACK to the previous directory - the history again appears and in .

it and in  .  - only  the client.

Git Reference wrote:

10.10 Git Internals - Moving Files
Moving Files
Unlike many other VCS systems, Git does not explicitly track file movement. If you rename a file in Git, no metadata is stored in Git that tells it you renamed the file. However, Git is pretty smart about figuring that out after the fact

11

Re: GIT transfer of files from one in another with history saving

I read this phrase of 200 times)) and and did not understand))  a broad gull -  history SHOWS.))  the web client - is not present.
I will repeat that to me not clearly -  a broad gull -   history whence locally. Or anyway all history will be and on remote ??
. It seems, you will not try - you do not learn. I will try to create pure  and to look, whether there is a history. I will try - I will unsubscribe.

12

Re: GIT transfer of files from one in another with history saving

Here https://stackoverflow.com/questions/231 … ir-history
It seems the second answer it is informative.

13

Re: GIT transfer of files from one in another with history saving

There it is written that brave and curve)) to try certainly costs however, at me all the same a question through  the broad gull  remains on remote  or not.