mirror of
				https://github.com/SoftFever/OrcaSlicer.git
				synced 2025-11-02 20:51:23 -07:00 
			
		
		
		
	Removing Slic3r name and links
This commit is contained in:
		
							parent
							
								
									7806df7664
								
							
						
					
					
						commit
						4b25d36df6
					
				
					 1 changed files with 6 additions and 6 deletions
				
			
		
							
								
								
									
										12
									
								
								.github/CONTRIBUTING.md
									
										
									
									
										vendored
									
									
								
							
							
						
						
									
										12
									
								
								.github/CONTRIBUTING.md
									
										
									
									
										vendored
									
									
								
							| 
						 | 
				
			
			@ -1,13 +1,13 @@
 | 
			
		|||
Did you encounter an issue with using Slic3r? Fear not! This guide will help you to write a good bug report in just a few, simple steps.
 | 
			
		||||
Did you encounter an issue with using PrusaSlicer? Fear not! This guide will help you to write a good bug report in just a few, simple steps.
 | 
			
		||||
 | 
			
		||||
There is a good chance that the issue, you have encountered, is already reported. Please check the [list of reported issues](https://github.com/alexrj/Slic3r/issues) before creating a new issue report. If you find an existing issue report, feel free to add further information to that report.
 | 
			
		||||
There is a good chance that the issue, you have encountered, is already reported. Please check the [list of reported issues](https://github.com/prusa3d/PrusaSlicer/issues) before creating a new issue report. If you find an existing issue report, feel free to add further information to that report.
 | 
			
		||||
 | 
			
		||||
If possible, please include the following information when [reporting an issue](https://github.com/alexrj/Slic3r/issues/new):
 | 
			
		||||
* Slic3r version (See the about dialog for the version number. If running from git, please include the git commit ID from `git rev-parse HEAD` also.)
 | 
			
		||||
If possible, please include the following information when [reporting an issue](https://github.com/prusa3d/PrusaSlicer/issues/new):
 | 
			
		||||
* PrusaSlicer version (See the about dialog for the version number. If running from git, please include the git commit ID from `git rev-parse HEAD` also.)
 | 
			
		||||
* Operating system type + version
 | 
			
		||||
* Steps to reproduce the issue, including:
 | 
			
		||||
    * Command line parameters used, if any
 | 
			
		||||
    * Slic3r configuration file (Use ``Export Config...`` from the ``File`` menu - please don't export a bundle)
 | 
			
		||||
    * PrusaSlicer configuration file (Use ``Export Config...`` from the ``File`` menu - please don't export a bundle)
 | 
			
		||||
    * Expected result
 | 
			
		||||
    * Actual result
 | 
			
		||||
    * Any error messages
 | 
			
		||||
| 
						 | 
				
			
			@ -17,5 +17,5 @@ If possible, please include the following information when [reporting an issue](
 | 
			
		|||
 | 
			
		||||
Please make sure only to include one issue per report. If you encounter multiple, unrelated issues, please report them as such.
 | 
			
		||||
 | 
			
		||||
Simon Tatham has written an excellent on article on [How to Report Bugs Effectively](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html) which is well worth reading, although it is not specific to Slic3r.
 | 
			
		||||
Simon Tatham has written an excellent on article on [How to Report Bugs Effectively](http://www.chiark.greenend.org.uk/~sgtatham/bugs.html) which is well worth reading, although it is not specific to PrusaSlicer.
 | 
			
		||||
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue