Unwanted uncommited changes about catalogue-development HOT 6 CLOSED

Ok, but didn't you open them in editor at least once?

Technical: As far as I can see some internal Java serialization processor changed it's behaviour (it's now closer to standardized behaviour), and additionally BattleScribe automatically saves file in new format even if you only opened it.

Non-technical language: These changes will probably occur for most of us sooner or later. We should just once commit them and get on with it. :)

from catalogue-development.

No, not at all! I haven't opened the SoB-file for months.
They just sit there in my Dropbox, changing the " to "
I have no problem with commiting them, but I was not sure what it would do to the files, etc.

from catalogue-development.

Ok, so probably BS reformats them just while indexing the directory, IDK really :)

Just commit, it's fine. Hopefully we won't be recommiting them this way and back, because someone got older BScribe ;D

from catalogue-development.

I just allowed Github to make all the commits.
Let's find out what happens! If they get changed back it will at least give me another clue on what could cause it.

from catalogue-development.

Ive had this happen to me as well lately.

On Monday, December 15, 2014, Tim Sijben [email protected] wrote:

I just allowed Github to make all the commits.
Let's find out what happens! If they get changed back it will at least
give me another clue on what could cause it.

—
Reply to this email directly or view it on GitHub
#8 (comment)
.

from catalogue-development.

Long-time deprecated.

from catalogue-development.