Jakob Reschke

This is only relevant when you use the FileSystem copy operations on files in the GitFilesystem. Your files should not be copied on each commit, unless your extension explicitly writes...

I would say this depends on #149 .

# Workaround For now you have to make sure that the current version in the Git browser already contains the non-Squeak files (such as a README) before you perform a...

When you pull, the upstream changes to those external files are currently lost if there is a real merge. So this only works because there is no real merge, but...

You did not give a link to the repository, so I can only guess what it is from the description. So far, I assume it is a duplicate of #53....

@MerlindlH I'm sorry, but I do not understand your request. What do you mean with commit history "textbox" (the commit list currently is a list view, or technically a tree...

Thank you, I understand now. But I don't think this is a high priority issue. Mostly because it is advised (by git) that the headline of a commit message should...

Stoopid metaprogramming breaks my brittle caller reflection, how sad! And I thought I would not make that #warn:-mistake again. Guess I should turn that warning into a comment, right?

Probably a duplicate of #53. We should document workarounds there. tl;dr: during merges, the Git browser (or rather the code behind it) currently does not pay attention to any files...