From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A7CC5385828B; Mon, 13 Jan 2025 05:26:20 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A7CC5385828B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1736745980; bh=O8briWHdx24tNCDKem6lFsvTrIPRTjlrtoA72s3N1RE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=nlqiKEvfzwDcSXgOj2FhyAZYTtgFfsp5SbBn2j0Td8ngYFIkqZF5jERF5atIDnGvK 37zgCT+odteD3uurFg5xOGTo+ubUgwJBTP8CArcQ+2UVhYTgOHDQD7zNg6+n71pTDz LeIRf4CEWhs696UmUL0jNmL0pG0ym/lDigIaarx8= From: "simon.marchi at polymtl dot ca" To: gdb-prs@sourceware.org Subject: [Bug build/30098] Keep trying clang-format Date: Mon, 13 Jan 2025 05:26:20 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simon.marchi at polymtl dot ca X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30098 Simon Marchi changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simon.marchi at polymtl do= t ca --- Comment #10 from Simon Marchi --- I was thinking that we could still commit a .clang-format to our repo, as t= he "current best approximation" of the config for our code style, with a comme= nt warning that it should not be blindly trusted. It can be improved with tim= e, and it can even be useful right away. For instance, I sometimes run git-clang-format on my patches, and then selectively add the good changes with "git add -p". It does find some mist= akes or some better way to format things (like removing an unnecessary line wrap= ).=20 I also use it through VSCode to format specific code sections. Again, the output is not to be trusted blindly, but it's often useful. --=20 You are receiving this mail because: You are on the CC list for the bug.=