public inbox for newlib-cvs@sourceware.org
help / color / mirror / Atom feed
From: Sebastian Huber <sh@sourceware.org>
To: newlib-cvs@sourceware.org
Subject: [newlib-cygwin] Clean up the vcs ID strings
Date: Fri, 01 Feb 2019 09:39:00 -0000	[thread overview]
Message-ID: <20190201093942.110778.qmail@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=0e7db0c356c0c47e34bd2cac1d3b83386540a7f7

commit 0e7db0c356c0c47e34bd2cac1d3b83386540a7f7
Author: jhb <jhb@FreeBSD.org>
Date:   Tue Jul 3 17:31:45 2018 +0000

    Clean up the vcs ID strings
    
    in libc's gen/ directory.
    
    - Move CSRG IDs into __SCCSID().
    - When a file has been copied, consistently use 'From: <tag>' for strings
      referencing the version of the source file copied from in the license
      block comment.
    - Some of the 'From:' tags were using $FreeBSD$ that was being expanded on
      each checkout.  Fix those to hardcode the FreeBSD tag from the file that
      was copied at the time of the copy.
    - When multiple strings are present list them in "chronological" order,
      so CSRG (__SCCSID) before FreeBSD (__FBSDID).  If a file came from
      OtherBSD and contains a CSRG ID from the OtherBSD file, use the order
      CSRG -> OtherBSD -> FreeBSD.
    
    Reviewed by:	imp
    Differential Revision:	https://reviews.freebsd.org/D15831

Diff:
---
 newlib/libc/posix/scandir.c | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/newlib/libc/posix/scandir.c b/newlib/libc/posix/scandir.c
index 2f00d3d..97a16cf 100644
--- a/newlib/libc/posix/scandir.c
+++ b/newlib/libc/posix/scandir.c
@@ -31,9 +31,8 @@
  * SUCH DAMAGE.
  */
 
-#if defined(LIBC_SCCS) && !defined(lint)
-static char sccsid[] = "@(#)scandir.c	5.10 (Berkeley) 2/23/91";
-#endif /* LIBC_SCCS and not lint */
+#include <sys/cdefs.h>
+__SCCSID("@(#)scandir.c	8.3 (Berkeley) 1/2/94");
 
 /*
  * Scan the directory dirname calling select to make a list of selected


                 reply	other threads:[~2019-02-01  9:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190201093942.110778.qmail@sourceware.org \
    --to=sh@sourceware.org \
    --cc=newlib-cvs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).