Community
Participate
Working Groups
Version: 3.2.0 Build id: I20060216-0800 Offering the possibility to compute a patch from compare view (when comparing different versions on repo) would ease backporting of changes into different streams.
will anything be happening here for 3.2?
This is not really what I would consider polish at least from the standpoint of the amount of work (i.e. we will not be able to reuse much of the exisitng Create Patch infrastructure since it is tied to the workspace). We will investigate and if it is a reasonable amount of work, we will do it.
Won't have time for this is 3.2 so moving to 3.3.
*** Bug 153090 has been marked as a duplicate of this bug. ***
There are three different scenarios to consider: 1) Creating a patch from two remote versions of a project. This could be made available in the Repo view or in the Compare Editor that is opened from the repo view. 2) Creating a patch by comparing one or more workspace projects with a branch or version. The best place for this would be the synchronize view. 3) Creating a patch by comparing a remote file with a file on disk but not necessarily in an Eclipse project (see bug 152986).
*** Bug 152986 has been marked as a duplicate of this bug. ***
(In reply to comment #6) > *** Bug 152986 has been marked as a duplicate of this bug. *** wrt 152986, what I would like to be able to do is submit a "proposal" to the development team in the form of a patch without having to checkout the entire project. 152986 asks that I be able to create a patch from the CVS repository perspective. Since create patch is linked closely with workspaces, perhaps you could address 152986 by allowing me to compare an arbitrary file in my project with an arbitrary file in cvs. Some variation of "compare with each other" in which I do the following: 1. open a file from cvs repository view 2. save the file to my project 3. make desired changes and save 4. Magically create patch based on my project file and some arbitrary file in CVS. Today, if I want to propose a change to docs, I can describe it as "change the second word of the third paragraph of topic after the word 'bla' ..." to "some proposed text". That may be ambiguous, so I can checkout the entire project, and create a patch for the file. The point of bug 152986 is to be able to give the developer a clear description of a proposed change via a patch *without* having to checkout the entire project. HTH
Unfortunately, we will not have the cycles to address this in 3.3. Patches are welcome;-)
Lowering priority to better match reality.
(In reply to comment #5) > There are three different scenarios to consider: > > 1) Creating a patch from two remote versions of a project. This could be made > available in the Repo view or in the Compare Editor that is opened from the > repo view. > > 2) Creating a patch by comparing one or more workspace projects with a branch > or version. The best place for this would be the synchronize view. > > 3) Creating a patch by comparing a remote file with a file on disk but not > necessarily in an Eclipse project (see bug 152986). Note that, scenarios based on generating a diff from a comparison are cover by bug 71374.
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. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
Still open. Can't remove "stalebug"
