Quote from: Griffith on October 06, 2016, 04:47:23 PM

Quote from: midnight_miner on October 06, 2016, 04:36:23 PM

Quote from: c00p3r on October 06, 2016, 12:32:26 PM

Quote from: Griffith on October 06, 2016, 05:46:58 AM

but i tried it like 3 times after i made sure the code matched the same system bitcoin was using and it worked every time. as long as its fixed i dont see too much of an issue that i couldnt actually find an issue XD

Because it was already done https://github.com/madzebra/Fly-coin/commit/53f2c176a102df8a667653164b1f4cd67a33a59c

The history was lost while transitioning to new repo.

Nice find c00p3r!

I guess changes and history would not get lost if Fly developers would follow the simple and easy Git development process and use Fork, Branch, and Pull Requests, to keep the code change history linked.

we do. but what do you do when the git acc owner completely deletes the main git? you have to start a new one. and thats what i did because thats what happened. the original git was rehosted from someones locally stored copy later, but for about 2 weeks over the summer it was gone. moved main repos after that incident

I can confirm this is true. But really, I dont see the importance of this or the discussion of zapwallettxes. Lets discuss the future of Fly, and answer and questions regarding upcoming changes like Flynode and POSO.

Vegas