I'll miss them, but only from a nostalgia standpoint. If those kinds of values are stored in strings, as opposed to comments, there are UNIX commands that can find them and report the current version of each module in an executable. That was handy in cases where a system/service administrator had some release management issues. It was also sometimes handy when working with vendors in trying to determine what patch level a product was at when for some reason the IT department had lost track of patches applied.
On Tue, Apr 10, 2012 at 12:00 PM, Drew Wills <[email protected]> wrote: > +1. I also get distracted by those pretty regularly. > > I can learn anything I need to by running a few git commands. > > drew > > Sent from my ASUS Eee Pad > > Eric Dalquist <[email protected]> wrote: > >>After dealing with this in 'yet another diff' the $Revision$ CVS/SVN >>keyword is on my hit list. Anyone have any objections to doing a mass >>delete of that line in all files for 4.1? >> >>-Eric >> >> > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/uportal-dev -- Bruce Tong Software Engineer Office of Information Technology Ohio University -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
