Community
Participate
Working Groups
A reasonable use case is: - external contributor without commit rights does some work - compares project he's working in against latest/base so he can see which resources he's modified - wishes to produce a patch of these Essentially, we rely on the user finding the files by hand to patch. Supporting it in the compare would be good. Note syncing with the repo doesn't help because: 1. you can't do patch there 2. you can only "Show in Navigator" on single selection (will enter seperate PR for that)
*** Bug 16010 has been marked as a duplicate of this bug. ***
later
Reopening
I would find it convenient it to also have "Create Patch" in the "CVS Resource History View". But of course it's sufficient to have it in the "Compare View".
I'm voting for this enhancement, wondering if it is on anyone's to-do-soon list :-). Sometimes you can get hold of source code, but not through anonymous CVS access. In those cases, access to diff/create patch through the UI, to create a patch from a (self-maintained) pre/post version, would be very useful for submitting patches.
This is supported in 3.0. You can patch from the synchronize view.
Hi Jean-Michel, thanks for your comment. My support for this enhancement was perhaps based on a slightly different basis than the original poster. I was hoping that patch creation could be achieved _without_ the base version being a CVS resource, i.e. allowing two non-version- controlled resources to be diffed (currently available through Compare), but to be able to then go on and create a patch for the diff.
Hello, I am also voting for 'Create patch' in Synchronize View. Although this operation is present in right-click menu for 'Team -> Synchronize with Repository...' or 'Compare With -> Latest from HEAD', it does not show up for 'Compare With -> Another branch or version'. I have a use case for 'Compare With -> Another branch or version'. Two friendly companies have their teams working on the common project. Both teams have no access to cvs repository of the other team. Each team has its "own" module for their part of project in their cvs and import foreign sources for second part of project to "foreign" module in their cvs. Each team is commiting changes to its own code and send changes to foreign code as patches. Patches are created as diff between import tag and patch tag in foreign module.
For the usercase above another alternative would be as follows: Go to CVS repositories view, in 'Configure Branches and Version...' select and add comparing versions (tags), then select both versions in the CVS repositories tree and run 'Compare' from right-click menu. Then select 'Create patch' in Compare window. Another shorter alternative is not to select 'Compare' in the tree menu but select 'Crate patch' tree menu.
