![]() ![]() #Tortoisehg push command returned code 1 PatchJust as with Git and GitHub, if you want to send a patch to a project on SourceForge, you first need to fork the code (i.e. This is similar to the default GitHub view, and is where you can browse the code, view branches and commits, and fork the project. Start by clicking the Code tab in the project, which for the Sasa project takes you to. The project landing page is much more focused on downloads and project activity (and Ads □) but overall the process of submitting a patch should be quite familiar in principal if you're used to GitHub. Unlike GitHub, where the code is front-and-center when you view a repository, it feels like you have to go hunting a bit further on SourceForge. I'm sure I've downloaded a few things here and there, but I've certainly never hosted, contributed, or even really looked at any projects on there. I've pretty much gone my whole life barely using SourceForge. Then I realised the project was hosted on SourceForge, and uses Mercurial for version control. I envisioned a 20 minutes piece of work, tops. NET Standard 1.3, I thought I'd help out by making the update, and sending a PR. Given all the hard work had been done to convert Sasa to use. To this (note the s in TargetFrameworks) netstandard1.3 netstandard2.0 net461 net472 If you already have a library targeting netstandard1.3, then adding the extra targets is pretty easy: just change this line in your. net472 to "override" the previous net461 target, as.net461 to avoid issues caused by net461's "fake".netstandard2.x to avoid large dependency trees in.netstandard1.x for maximum compatibility. ![]() If you follow the official advise on cross-platform targeting to its conclusion, eventually you end up targeting at least four frameworks: Unfortunately that can cause issues for people targeting net461. To work around this issue for consumers, library authors can add an additional netstandard2.x target to their library. Unfortunately, if you're using a platform that supports netstandard2.x, then referencing a netstandard1.x package can result in a huge dependency tree being dumped in your folder output. He did a great job supporting a wide range of platforms by targeting. The library has been around for a long time (since 2013), and at the start of 2019, Sandro Magi added. It contains a variety of utility types, but we use it primarily for the implementation of functional concepts like Option. NET Standard supportĪt Elevate Direct, we use a library called Sasa quite extensively in our. It's sometimes easy to forget there's a world outside of Git and GitHub, and it was interesting dipping a toe in! The motivation: improving. ![]() In this post I describe my experience of making my first contribution to a project on SourceForge, using the Mercurial version control system. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |