Slow operation, more of a question about git-tfs HOT 4 OPEN

The initial clone can take a while, especially if there are a lot of changesets e.g. a project with a lot of history.

Directly after a git-tfs rcheckin you should be update-to-date, so there shouldn't be a need to git tfs pull --rebase.

Overall, what you describe sounds unusual, the git tfs pull --rebase should be fast.

One thing which comes to mind is: Did you use cherry-pick or rebase of already commited changesets in tfs (represented as git
commits) onto a branch which you then did run the rcheckin on?

Because if you did, and didn't remove the lines similar to git-tfs-id: [http://some.server.com/tfs/tpc/]$/some/path;C12345
in the cherry-picked/rebased commits, then this might confuse git-tfs.

from git-tfs.

I do not think so. I am not capable of answering. If I understand you right is that you think I might try to checkin a commit that is a cherry pick of an already existing commit.

from git-tfs.

Your understanding is correct. My assumption is that you were trying to checkin something which git-tfs thinks is already checked in (due to the git-tfs-id)

from git-tfs.

It seems like if there is some change in another branch than the one checked in and I use git tfs pull --rebase all files in the other branch are downloaded. I might be wrong.

from git-tfs.