You should've just made a fork.

[Crayder]

Instead of creating a new repo without all of the commit history and shit you should've just cloned one of the existing forks or even imported the entire repo from the already existing git sources.

[Crayder]

Specifically this one, which is the official one from Y-Less.

https://github.com/Misiur/sscanf-3.0

Emmet_ hadn't updated any of it yet anyways. And yes, it's the source for 2.8.2. It also includes 3.0's source.

[maddinat0r]

To be quite honest with you, I don't care.
I know there already are repositories with the sscanf code for both versions. Well, I just made another one. Yes, it doesn't have any original commits made by Y_Less, so what? Does this give me a major disadvantage in maintaining this plugin? I think not.

[Crayder]

Yeah, actually it does give you a few major disadvantages. If you really want to start completely fresh that's on you though, not me. I was just suggesting the easier way of doing this.

[maddinat0r]

Well, instead of just saying that it gives me disadvantages, could you explicitly list them?

[Crayder]

There's not really much of a point now, you've already began committing.

• Restoration
• Understanding where specific things happened
• Knowing why certain things were added or removed
• Knowing when things happened
• The backups from before the latest commits that you have
• Knowing who did what
• For the people who have contributed
• ...
• ...
• ...
• Basically all of the reasons version control was invented and all of the reasons you are using GITHUB.

Obvious, small things like these do make a difference.

[maddinat0r]

I'll make sure everyone who has contributed to that project gets mentioned.
Other than that, those points would probably hinder me a bit if I'd continue developing this plugin feature- or performance-wise. However, I only intend to fix bugs, so there's not really a drawback here.