Date: Fri, 8 Jan 2021 18:32:51 +0000 From: Alexander Best <arundel@freebsd.org> To: Polytropon <freebsd@edvax.de> Cc: freebsd-questions@freebsd.org Subject: Re: Possibly malformed date in several manual pages Message-ID: <20210108183251.GA71246@freebsd.org> In-Reply-To: <20210108131811.357f173c.freebsd@edvax.de> References: <20210107080827.GA10295@freebsd.org> <20210108113505.GA41405@freebsd.org> <20210108131811.357f173c.freebsd@edvax.de>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Fr. Jan. 8 2021, Polytropon wrote: > On Fri, 8 Jan 2021 11:35:05 +0000, Alexander Best wrote: > > "$Date:" and "$" in the vacation-example of course aren't pretty to have in a > > manual page, but I crosschecked with Linux and here those terms are also > > displayed at the end of the according manual page. > > > > One might could take care of this during the installation process of the manual > > pages, but it's probably not worth the hassle. > > Just a question: > > It looks like "$Date: <something> $" is expanded from the $Date$ > header known in CVS (among others). With the transition to SVN > and now to Git, wouldn't those be subject to being converted into > Git's own human-readable headers, making the date information > known to the version control system, or maybe "overwriting" them > with its own timestamp? Or are they kept "as is" when importing > sources from other version control systems (like RCS, CVS, SVN)? Hi Polytropon, that's a valid question. I'm not sure, to be honest. Looking at older *.c files withing the FreeBSD repository which originated from 4.*BSD or UNIX shows some legacy vcs-tags. These however mostly appear in the initial copyright statement and thus don't affect the code (or the manuals). [1] on the other hands states the following: "The dist tree can be cleaned up as necessary. Disabling keyword expansion is recommended, as it makes no sense on unmodified vendor code and in some cases it can even be harmful. OpenSSH, for example, includes two files that originated with FreeBSD and still contain the original version tags." One could of course get a snapshot (e.g. via svn) of some vendor import and try to remove the tags using `svn propdel svn:keywords -R .`? I wouldn't vote for removing legacy tags in general, but would like to see sensable TH-statements within those manual pages I mentioned. Kind regards, Alexander 1: https://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/article.html#subversion-primer, Section 5.4.4.1.2. (Cleaning Up). > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJf+KVRXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0NEFCRkJFNkIyOTQ5NkYzQzFFQTc5NDE3 RjQzRThCNkQ4OTM3NDUwAAoJEH9D6LbYk3RQQYwQAJKeZQqSf5rILIqSg+Uf+1oX T5BIa2jl3uhjeqoT72Jv5IY91XOA7/c7bNoktwUOHlQhOQojTaZqtUE97d6makP9 MODgw8KU2exHqGFgGwPPOupgtOOnE7Zbvno6Qw/WMf+6TwD9YVgZ6IN2kQIpfSJ7 Yg9Asxvls+pJQFHjjaxM0J+rGD9Qtc6f3IU6y1gZ0Y4qcCbQCGcsgRqQyijn7TFc oavcckld509NbwCQG6YHjzsK4tBtczwETpamtfdlntKAY/cuZqmcOYrNZRYOgqdj Lu8GT8RyX+bkIav+7SAV2ReBC4oyCCSewgwAgZ4m5WdZBl4Fs1+ZU2YLbytlvkgT xE2yDoljBykJO0FG5KdH8D6RHlyUcsMfg479MjnDE83NM+t7hdDIX/s37o+e7PsW 0ZZc5A1rNdjRE5HimOQBEHAlGUpBiAZ5lX//7Tz2G/NnoSADvIIrqquAYeM7Ygc8 kmMxJy5ERThBmGRZXDNG9WYKYh7TDfwcINu4jAgZ5Nv1jGr7xwRO2kPfYCtmYehC kdERxX2O3FEypZv+ziKD9aeoI2SOwXBTeBF4AtBcFR9MK7jjZjykLYyP49plbPY2 rMCaoqSRHxKlgLK2aglMK5zJf+hRBbLzgCciG54qpEclSt8ngqdHjE+t5+ltXgJf s+ai0cTBx8PNOsM+YyeS =hYSq -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210108183251.GA71246>