FLTK logo

Re: [fltk.general] Population of "$Id$" in FLTK source code

FLTK matrix user chat room
(using Element browser app)   FLTK gitter user chat room   GitHub FLTK Project   FLTK News RSS Feed  
  FLTK Apps      FLTK Library      Forums      Links     Login 
 All Forums  |  Back to fltk.general  ]
 
Previous Message ]New Message | Reply ]Next Message ]

Re: Population of "$Id$" in FLTK source code duncan Apr 22, 2020  
 
On Wednesday, April 22, 2020 at 12:14:26 PM UTC+2, Albrecht Schlosser wrote:
 
I know this is not really the place to discuss it, but anyway: I could
imagine to remove the $Id$ string at the top of the file and expand it
at the end of the file to just something like "End of <filename>"
because that was one of the reasons in the original concept: show that
the file is complete. OTOH, this might have been an issue in times when
files were transferred with insecure protocols via modems and no longer
today.

What do other devs and users think? Should we remove the $Id$ tags
completely, or anything else?


Why not just start to replace expanded $Id$ tags with a literal $Id$ just
as and when individual files are committed? Just like copyright year.
That way the Source Documentation rules in the CMP wouldn't change.
Maybe it would be possible to add a commit filter to check?

Are the $Id$ tags actually being used or checked by anything?
If not, change the CMP and slowly start removing them.

D.

--
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/37f2c676-d6e3-476a-8b8d-f82dfcfdb0d7%40googlegroups.com.
Direct Link to Message ]
 
     
Previous Message ]New Message | Reply ]Next Message ]
 
 

Comments are owned by the poster. All other content is copyright 1998-2024 by Bill Spitzak and others. This project is hosted by The FLTK Team. Please report site problems to 'erco@seriss.com'.