- From: G. Wade Johnson <gwadej@anomaly.org>
- Date: Sun, 7 Feb 2010 09:58:17 -0600
- To: Jeff Schiller <codedread@gmail.com>
- Cc: SVG IG List <public-svg-ig@w3.org>
On Sun, 7 Feb 2010 09:42:22 -0600 Jeff Schiller <codedread@gmail.com> wrote: > Yes, sorry I wasn't being clear. I'm aware of CVS working > line-by-line and the HTML not caring about line breaks :) <grin>I figured you did.</grin> But, since we have some people new to version control systems on the list, I thought it was worth being more explicit. > What I'm looking for is a tool that would highlight the differences > (red/green) or something. Kind of like this: > > http://code.google.com/p/svg-edit/source/detail?r=1354 > > (click the + next to the file to see what I mean) I've seen a few tools built on top of CVS for doing this sort of thing in the past. (Including tool-assisted code-review systems that are really nice.) > I'll also note that having a web-based system like this also allows > people to comment on the revision directly and get email > notifications. Very convenient. Does anyone know if the W3C has anything like that available? G. Wade > On Sun, Feb 7, 2010 at 9:24 AM, G. Wade Johnson <gwadej@anomaly.org> > wrote: > > On Sat, 6 Feb 2010 16:14:50 -0600 > > Jeff Schiller <codedread@gmail.com> wrote: > > > >> I started reading the primer today, got through chapter one and > >> made a few minor corrections here or there. I'm really trying to > >> get a sense as to how a review process can proceed, ideally I'd > >> like to give reviewers the possibility of making changes > >> themselves in the HTML doc and then sending a diff (patch) to the > >> editor/owner (whoever that will be). > >> > >> My CVS is a little rusty, but I did do a cvs diff and took a look > >> at what my changes show: > > > > I remember that a lot of people preferred the "unified diff" for > > looking at changes. So much so, that most of the systems that came > > after CVS use it as a default. > > > > cvs diff -u > > > > On a Unix-based system, you can make this the default by adding the > > line: > > > > diff -u > > > > to the file .cvsrc in your home directory. > > > > Apparently, TortoiseCVS has the same ability. The FAQ says you can > > find the .cvsrc file from CVS -> Preferences. > > > > As for the difficulty seeing the changes, it's not real surprising > > since CVS diff work line by line. Since the paragraph is all on one > > line, that makes the diff harder to read. HTML doesn't care about > > line breaks, so we could add line breaks to wrap the paragraphs > > into shorter lines. That makes the diffs easier under some > > circumstances, but it does make those of us with a bit of OCD > > likely to spend time reformatting paragraphs.<shrug/> > > > > Trade-offs abound. > > > > G. Wade > > -- > > Results are what you wanted, consequences are what you got. > > -- Michael VanDusen > > > -- You forgot the first rule of the fanatic: when you become obsessed with the enemy, you become the enemy. -- Jeffrey Sinclair in "Infection"
Received on Sunday, 7 February 2010 15:58:53 UTC