| Summary: | CVS diff should use (or at least allow) -p option | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Jennifer Hodgdon <yahgrp> |
| Component: | CVS | Assignee: | platform-cvs-inbox <platform-cvs-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | tomasz.zarna |
| Version: | 3.4.1 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Jennifer Hodgdon
afaik -p is for C functions only, so to get a bigger audience I would suggest adding support for -F which works with regexes (e.g. ‘^[[:alpha:]$_]’ for C). What do you think? -p actually works OK (not perfect but OK) for PHP as well as C, and it is fairly standard in PHP open-source projects to use diff -up. Probably other languages using C-like syntax (Java, etc.) would also work OK with -p, but I don't have direct experience with them to verify. How about just adding the generic ability to put additional command-line options on the cvs diff command, so that I could use -up, and others could use -f? Well, we cannot be too flexible here because we must be able to consume our own patches (generated with Eclipse) i.e. we must be able to parse such patches and apply them. That makes sense. -p certainly doesn't pollute patches for Eclipse... 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. |