From nobody Fri Nov 5 03:03:05 2021 X-Original-To: standards@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id E48BC1840686 for ; Fri, 5 Nov 2021 03:03:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HllgY62jpz4gMj for ; Fri, 5 Nov 2021 03:03:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id B121310497 for ; Fri, 5 Nov 2021 03:03:05 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 1A5335n1064004 for ; Fri, 5 Nov 2021 03:03:05 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 1A5335ZQ064003 for standards@FreeBSD.org; Fri, 5 Nov 2021 03:03:05 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: standards@FreeBSD.org Subject: [Bug 216862] C11 conformance: cexpl() is missing Date: Fri, 05 Nov 2021 03:03:05 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: standards X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: imp@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: standards@FreeBSD.org 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: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Standards compliance List-Archive: https://lists.freebsd.org/archives/freebsd-standards List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-standards@freebsd.org X-BeenThere: freebsd-standards@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216862 Warner Losh changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |imp@FreeBSD.org --- Comment #6 from Warner Losh --- (In reply to Steve Kargl from comment #5) It does pickup new files.... However, it's complicated. 'git add' puts the file into a logical staging a= rea, and git diff excludes those not-yet-committed-but-in-the-staging-area files= by defualt. git diff --staged will get them, but it's not so straight forward to use. But 'git diff HEAD' often will as well, but there's some edge cases that I can't recall right now. You're better off doing a 'git checkout -b new-bug' and committing it. Then= you can create your diff with 'git diff main' or better yet, you can create a p= atch with all the commit data: your name, the commit message, etc' with 'git format-patch --stdout main..new-bug > patch-file-to-upload-to-bugizlla'. Th= is will produce output that's suitable for others to use 'git am' to just snar= f it it into the tree. Without the --stdout, it will create a bunch of numbered files, one per commit which is something you might not want. Then, you can do a 'git checkout main' and get back to the pristine tree. If time passes and you need to make a change, you can update your local main, = then use 'git rebase -i main new-bug' and it will move the change forward to the= tip of the FreeBSD tree, which will let you resolve any conflicts that may have cropped up. git rebase also lets you curate patches since you can reword the commit message, split apart commits, or combine different ones depending on what's needed. The other option is to create a pull request on github, which some find eas= ier, though the first time setup can be a bit weird. --=20 You are receiving this mail because: You are the assignee for the bug.=