From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29]) by sourceware.org (Postfix) with ESMTPS id E7C313858413 for ; Fri, 7 Jan 2022 10:25:51 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org E7C313858413 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=suse.cz Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=suse.cz Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out2.suse.de (Postfix) with ESMTP id B8A221F397 for ; Fri, 7 Jan 2022 10:25:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1641551150; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=7sf/242fErN7winvqTuzZUOSEm4iOODUEdXFfo80a8Y=; b=vFHNlG8xB5vatlASkmFq+qK7l8SE1KmFL8jX2K3kBS9qfLbQ1bKZa7k+wfO/lJklM0/meJ B//WMr87Ze38p0xomdWjAtnFMnXhdvYYUan9hiwde2CTL2vBkXgI6FWreCBa68xG+YZl78 m3Qsqk8w/7ar6kuG5RwSjmtg0FsJ7ck= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1641551150; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=7sf/242fErN7winvqTuzZUOSEm4iOODUEdXFfo80a8Y=; b=bS2+p5bbypxUDoqio706gt+wUgeRRJ2QSHUz/qu6DxvU0IpluDX8Ry2h4MaMKfNEBuxYVX HJGVGFcaKmCC4ODw== Received: from suse.cz (virgil.suse.cz [10.100.13.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by relay2.suse.de (Postfix) with ESMTPS id A59BEA3B88; Fri, 7 Jan 2022 10:25:50 +0000 (UTC) From: Martin Jambor To: GCC Mailing List Subject: Mass rename of C++ .c files to .cc suffix? User-Agent: Notmuch/0.34.1 (https://notmuchmail.org) Emacs/27.2 (x86_64-suse-linux-gnu) Date: Fri, 07 Jan 2022 11:25:50 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-5.2 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jan 2022 10:25:53 -0000 Hi, Would anyone be terribly against mass renaming all *.c files (that are actually C++ files) within the gcc subdirectory to ones with .cc suffix? We already have 47 files with suffix .cc directly in the gcc subdirectory and 160 if we also count those in (non-testsuite) subdirectories, while the majority of our non-header C++ files still has the .c suffix. I have already missed stuff when grepping because I did not include *.cc files and the inconsistency is also just ugly and must be very confusing to anyone who encounters it for the first time. Since we have switched to git, this should have quite small effect on anyone who does their development on branches. With Martin Li=C5=A1ka we d= id a few experiments and git blame, git rebase and even git gcc-backport worked seamlessly across a rename. I would be fine waiting with it until GCC 12 gets released but see little value in doing so. What do others think? (Any important caveats I might have missed?) Martin