|
And that comes down to tooling. I don't know what RDi has as I spend 95% of my time doing work in Node these days.
However, in VS Code when I am working on an application, I have an extension called Git Blame installed. Whenever my cursor is on a line, I can look at the bottom of the IDE and it will say "Blame Joe Pluta (2 months ago)" for example. If I need more info, I simply click that "Blame" line and the repo, GitHub in our case, opens with all of the info about that commit. So I see changes to that file and any others that were changed in that commit as well as the description for that commit.
So I actually get all the info you mention and more without scrolling up to the top of the program to look at the comments that go with a mod mark. I'm sure there is a plugin for Eclipse with similar functionality, but again, I don't spend enough time there to know.
Brian May
Director
Pre-Sales and Customer Solutions
Profound Logic Software
http://www.profoundlogic.com
937-439-7925 Phone
877-224-7768 Toll Free
November 12-14 • Orlando, FL
Three days of Profound Logic education with our experts!
Register now: info.profoundlogic.com/plus2019
-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Joe Pluta
Sent: Thursday, October 3, 2019 11:34 AM
To: rpg400-l@xxxxxxxxxxxxxxxxxx
Subject: Re: Full Free RPG and modification marks
It depends on shop standards. We require exactly the process you outline. If you don't, it's a severe breach of protocol. Not that it never happens, but it never happens without reason.
I agree that Git has benefits, but it also has drawbacks. As a simple case, if a mod adds a line, and a second mod deletes it, I don't know of an easy way to see both in a single display. And that view is often crucial when identifying why something acted one way for a month and then stopped acting that way.
Again, I'm not saying Git is bad. I'm just saying that mod marks have a real use.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.