Bug 307449 - Create Patch should use .patch file extension by default
Summary: Create Patch should use .patch file extension by default
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-29 16:53 EDT by Ralf Ebert CLA
Modified: 2019-09-06 16:13 EDT (History)
1 user (show)

See Also:

Attachments
Correctly named patch to name patches correctly (2.47 KB, patch)
2010-03-29 16:54 EDT, Ralf Ebert CLA 		no flags Details | Diff
307449.patch (2.80 KB, patch)
2010-03-29 17:18 EDT, Ralf Ebert CLA 		no flags Details | Diff
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ralf Ebert CLA 2010-03-29 16:53:12 EDT 
Naming patches "something.patch" makes them more recognizable by tools that can work with patches, the create patch wizard should therefore propose this file extension by default.
Comment 1 Ralf Ebert CLA 2010-03-29 16:54:15 EDT 
Created attachment 163329 [details]
Correctly named patch to name patches correctly
Comment 2 Ralf Ebert CLA 2010-03-29 17:18:49 EDT 
Created attachment 163331 [details]
307449.patch

Also changed default patch name to untitled.patch
Comment 3 Szymon Brandys CLA 2010-03-30 04:13:29 EDT 
Thanks Ralf for the patch.
I think that 'Save as type' should also offer 'Text file' and '*.*' in addition to the 'Patch' type. 'Text file' should be the default. Moreover, to be consistent, we should do similar changes to the Apply Patch wizard and Apply Patch in Sync View. I'm suggesting to prepare a patch that covers all those cases.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:13:30 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.