Submitted by Steve Purcell on Sat, 10/27/2007 - 08:37.
Antti-Juhani: Thanks for the feedback. The author issue is already fixed; I encountered it myself and fixed the issue, but hadn't pushed my changes up to the public repository.
Unless I'm misunderstanding what you mean, I think it's normal that the setpref commits would not be migrated to git, because there's no easy way to translate "boring" files etc. to .gitignore.
I'd imagine that a destination git repository would necessarily include one or more commits that would include git-specific repository customisations, e.g. .gitignore files.
Antti-Juhani: Thanks for the feedback. The author issue is already fixed; I encountered it myself and fixed the issue, but hadn't pushed my changes up to the public repository.
Unless I'm misunderstanding what you mean, I think it's normal that the setpref commits would not be migrated to git, because there's no easy way to translate "boring" files etc. to .gitignore.
I'd imagine that a destination git repository would necessarily include one or more commits that would include git-specific repository customisations, e.g. .gitignore files.