
Please be sure to disable any spam filters you may have for our website, so that email messages can reach you. If you have any problems with the Gnutella Forum registration process or your Gnutella Forum account login, please contact us (this is not for program use questions.) Your email address must be legitimate and verified before becoming a full member of the forums.


Registration is fast, simple and absolutely free so please, join our community today! (click here) (Note: we use Yandex mail server so make sure yandex is not on your email filter or blocklist.) By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content, fun aspects such as the image caption contest and play in the arcade, and access many other special features after your registration and email confirmation. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. In the same way that you would with any normal commit, you have to add all files and push to remote to save this state.

Add this version to the staging area and push to remote This will take you to the version you wanted to go back to in your local environment. ’ - You aren’t required to add this, and it may look like it has worked but if you leave this off it will take you to a new “detached head state” where you can make changes and it will allow you to make commits, but nothing will be saved and any commits you make will be lost. Use git checkout & the ID (in the same way you would checkout a branch) to go back: $ git checkout. Go back to the selected commit on your local environment Whichever option you use, take a note of the ID of the commit you want to revert to. Committing little and often, so that your change history is clear should save you from having to take this route. This is useful if you didn’t give yourself useful commit messages, or you’re just not sure exactly which version you need to go back to.
