Recent changes to wiki

HowTo: Eclipse EGit and the Projects modified by Dylan Myers

2015-08-19T23:16:18.761000Z

Choose File -> Import -> Git -> Projects from Git
Click Next
Choose the Clone URI
Click Next
Put in the appropriate git URI
git://git.code.sf.net/p/megamek/git
git://git.code.sf.net/p/megameklab/git
git://git.code.sf.net/p/mekhq/git
Click Next
Click Next
Choose a Location
Click Next
Wait for the clone process to finish
Select the option to import existing projects
De-select all the launch4j checkboxes
Click Finish

Solution 2: Mark database.yml as assume-unchanged in git’s index

In fact git has the power to ignore local changes to tracked files, but it’s slightly clunkier than and completely >inconsistent with the familiar .gitignore. You must use git update-index to tell git to ignore changes to the file:

$ git update-index --assume-unchanged config/database.yml

Now your git status will be clean, and you will have no unwanted results when you run things like git add . and git >commit -a. And when somebody upstream modifies database.yml, git will not ask you to resolve the conflict. Perfect.

To un-mark the file as assume-unchanged:

$ git update-index --no-assume-unchanged config/database.yml

And if you want a list of tracked files that git is ignoring:

$ git ls-files -v | grep ^[a-z]

bug_report_howto modified by Nicholas Walczak

2015-02-25T14:37:25.921000Z

--- v17
+++ v18
@@ -37,6 +37,7 @@
 In addition to attaching a log file, it is also helpful to attach a saved game.  If you have a saved game prior to the bug occurring, often the devs can load the saved game and quickly reproduce the bug.  This is very helpful as the dev can then attach a debugger and step through the code to figure out exactly what is going on.  Megamek automatically creates an autosave at the start of a turn and there is also the "paranoid save" option that will make Megamek save an autosave at the start of every phase instead of at the start of a turn. Changing the name of the save game (not the extension part) to the name of the player the dev should connect as would help streamline the devs effort to fix bugs. Do **not** say, "see this other ticket...** kind of comments. Attach relevant files to the ticket itself.

 Until further notice: Anon bug reports have been disabled. Thank you for your patience.
+This means that you will not see the option to create a ticket if you are not signed in, however anyone with a SourceForge account can sign in and submit tickets.

 **Subscribe to notifications if posting as anon**

bug_report_howto modified by Dylan Myers

2015-02-25T00:25:28.849000Z

--- v16
+++ v17
@@ -34,7 +34,7 @@

 **Attach a saved game**

-In addition to attaching a log file, it is also helpful to attach a saved game.  If you have a saved game prior to the bug occurring, often the devs can load the saved game and quickly reproduce the bug.  This is very helpful as the dev can then attach a debugger and step through the code to figure out exactly what is going on.  Megamek automatically creates an autosave at the start of a turn and there is also the "paranoid save" option that will make Megamek save an autosave at the start of every phase instead of at the start of a turn. Changing the name of the save game (not the extension part) to the name of the player the dev should connect as would help streamline the devs effort to fix bugs.
+In addition to attaching a log file, it is also helpful to attach a saved game.  If you have a saved game prior to the bug occurring, often the devs can load the saved game and quickly reproduce the bug.  This is very helpful as the dev can then attach a debugger and step through the code to figure out exactly what is going on.  Megamek automatically creates an autosave at the start of a turn and there is also the "paranoid save" option that will make Megamek save an autosave at the start of every phase instead of at the start of a turn. Changing the name of the save game (not the extension part) to the name of the player the dev should connect as would help streamline the devs effort to fix bugs. Do **not** say, "see this other ticket...** kind of comments. Attach relevant files to the ticket itself.

 Until further notice: Anon bug reports have been disabled. Thank you for your patience.

Discussion for bug_report_howto page

2014-12-28T19:39:48.579000Z

Since not everyone... (cough yeah Ralgith I'm staring at you... u heretic Linux user :) ) understands GREP searches which is what is used by SF. Perhaps a quick how to search document is in order... +VTOL +Firing generates a search that includes both, etc, ad nauseum.

bug_report_howto modified by Dylan Myers

2014-12-24T15:17:21.062000Z

--- v15
+++ v16
@@ -18,7 +18,7 @@

 After making sure the bug report isn't a duplicate, it's time to think about what makes a quality bug report.  It is important to be clear and detailed; the developers cannot read your mind and the only information they have to go off of is what is in the bug report.  Often, something that seems obvious to the reporter will not be obvious to the developer, because the developer can be in a different frame of mind.  Describe the situation leading up to the bug in as much detail as possible.  Also include steps to reproduce: these should be detailed steps that a developer can use to reproduce the bug (a saved game can help here, see below).

-One thing to note is that the bug tracker is not a forum to get information: if there is confusion about how something works, or why something works the way it does that isn't grounds for a bug report.  Instead, posting on the forums is a better way to get information: <http: megamek.info="" forums="">.  Furthermore, bug reports without sufficient details to reproduce are not beneficial at all.  They just waste the devs time. Bug reports with single sentence descriptions or descriptions that say things like "see title" will not be well received.  
+One thing to note is that the bug tracker is not a forum to get information: if there is confusion about how something works, or why something works the way it does that isn't grounds for a bug report.  Instead, [posting on the forums](http://megamek.info/forums) is a better way to get information.  Furthermore, bug reports without sufficient details to reproduce are not beneficial at all.  They just waste the devs time. Bug reports with single sentence descriptions or descriptions that say things like "see title" will not be well received.  

 It is also important to only report one issue per ticket.  Creating a new ticket is cheap and it's easy to cross reference tickets.  When multiple issues get reported in a single issue it just ends up confusing the discussion.

bug_report_howto modified by Dylan Myers

2014-12-24T15:15:33.764000Z

--- v14
+++ v15
@@ -6,6 +6,9 @@
 **Submit to Correct Location**

 Submitting a bug report to the correct location is important for getting it fixed quickly. While we can move tickets from one tracker to another, it can often slow down fixes. Additionally, forums, email, and private messages are not appropriate places for bug reports.
+[MegaMek Tickets](https://sourceforge.net/p/megamek/_list/tickets)
+[MekHQ Tickets](https://sourceforge.net/p/mekhq/_list/tickets)
+[MegaMekLab Tickets](https://sourceforge.net/p/megameklab/_list/tickets)

 **Check for duplicates**

bug_report_howto modified by Dylan Myers

2014-12-24T15:10:47.265000Z

--- v13
+++ v14
@@ -2,6 +2,10 @@
 -------------

 Submitting quality bug reports is important to get bugs fixed and to not waste developer time.  Once a bug is reported, a dev will have to verify that the report is actually a bug.  Once it has been verified, a dev has to hunt down the cause of the bug, and then fix it.
+
+**Submit to Correct Location**
+
+Submitting a bug report to the correct location is important for getting it fixed quickly. While we can move tickets from one tracker to another, it can often slow down fixes. Additionally, forums, email, and private messages are not appropriate places for bug reports.

 **Check for duplicates**

@@ -29,7 +33,7 @@

 In addition to attaching a log file, it is also helpful to attach a saved game.  If you have a saved game prior to the bug occurring, often the devs can load the saved game and quickly reproduce the bug.  This is very helpful as the dev can then attach a debugger and step through the code to figure out exactly what is going on.  Megamek automatically creates an autosave at the start of a turn and there is also the "paranoid save" option that will make Megamek save an autosave at the start of every phase instead of at the start of a turn. Changing the name of the save game (not the extension part) to the name of the player the dev should connect as would help streamline the devs effort to fix bugs.

-Until further notice: Anon bug reports has been disabled. Thank you for your patience.
+Until further notice: Anon bug reports have been disabled. Thank you for your patience.

 **Subscribe to notifications if posting as anon**

Discussion for bug_report_howto page

2014-12-06T20:43:53.355000Z

I have to do this at least once a month. Sorry for swearing... I am crazy (have the Doctor's Note and all) every once in awhile I TARFU my Meds and well... taduh! I write something seriously unacceptable. Sorry to Xenon and Ralgith and everyone else.

I feel bad :(

Which isn't to say something like this won't happen in the future... it will... such is the nature of my Crazy. I'll just come along and apologize for being a jerk again at sometime in the future. Just please, try to understand, I'm not doing it to BE A JERK and PISS EVERYONE OFF. Among a long list... this is a part of my Crazy... http://en.wikipedia.org/wiki/Tourette_syndrome

Sorry, I suck, I feel bad, there was no reason to get that off the wall, I am a bad person.

Sorry.

Discussion for bug_report_howto page

2014-12-05T22:33:09.210000Z

As SF is new to me, mistakes will happen. Arlith had already spotted it. Just a tiny slash was all it needed. ;)

Hopefully my noob period is a quick one. :)

bug_report_howto modified by Xenon54z

2014-12-05T21:12:52.247000Z

--- v12
+++ v13
@@ -29,7 +29,7 @@

 In addition to attaching a log file, it is also helpful to attach a saved game.  If you have a saved game prior to the bug occurring, often the devs can load the saved game and quickly reproduce the bug.  This is very helpful as the dev can then attach a debugger and step through the code to figure out exactly what is going on.  Megamek automatically creates an autosave at the start of a turn and there is also the "paranoid save" option that will make Megamek save an autosave at the start of every phase instead of at the start of a turn. Changing the name of the save game (not the extension part) to the name of the player the dev should connect as would help streamline the devs effort to fix bugs.

-Until further notice: Anon bug reports has been disabled. Thank you for your patience.
+Until further notice: Anon bug reports has been disabled. Thank you for your patience.

 **Subscribe to notifications if posting as anon**