From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id EC61F33CE8A; Thu, 28 May 2026 20:36:27 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780000588; cv=none; b=Q8noxd4XlHsPE/p6cH92LGlxPVQl37n+c93odOcMJLmLSjJXPYlq+0olNyciKeM0zqR5JPAy6axMTfYEQ6k6BV7AevSNRv5LX7ztBOFPN9Twj/M7JQRj1bCeLVAj5kQw1qhyZfzcFJpVhESPoX8pWNL2XGCquY4a5o7arYqZDyk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780000588; c=relaxed/simple; bh=BG7PcsOQ1fJd65tikquJGhW6e7ugLFVstmsuATfUSTE=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=f5ACeV/1aT/DKiT/MzE1l9Xj+oLZZpwSfo1XiLezwJavYAqZwZs1vBxgo+IQ1IqPAqrMwg7gA2MgyFxmCjD+txRz/5yhG0V1q/nQJkHjkQy0p3akLBM6RwuT2yUx5n7mBtOSB17+G/MOZSR1rH2TcR/z4SmCEMDUwsOSfNBLbN8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=YNgrhodh; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="YNgrhodh" Received: by smtp.kernel.org (Postfix) with ESMTPSA id A03541F000E9; Thu, 28 May 2026 20:36:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1780000587; bh=dH+Kn+7B9a9XzYvNmcr6RDiESxjU0RsDgQxo6qQZFCk=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=YNgrhodhhwC1jJ/or1n6DwQHbA8KvAEkfSpaIJFRIHkArjDa0109XiTf9PBm9gfS4 eDT2e7cO8yLW6UzDCe2k0NhPcV9UIhHTT2rJNcBzWwbT/lW1faV2IRE8ykkVzw8Kz1 YGs5FJ98dDBJDbgHtRmDzo3liDnydDuqDGCIgWGBplpfsQLxVr6c2oxei1HvPpg7mt Vf33QvjwxVYNdK9Yn6AgwNlxX2K83MuA/kurqDC8tXdRVrEGtX82LzA+/bgIyDxZE4 VwB6yoWtXNpRJJYnXsXC4YF5kSTEXtFQGwWwC6ejYQUmWhmjY7IUYGqwC+A/e7oyNa DMXWJ7iNTJyjg== Date: Thu, 28 May 2026 13:36:22 -0700 From: Nathan Chancellor To: Miguel Ojeda Cc: Manos Pitsidianakis , Nicolas Schier , Linux Kbuild mailing list , Miguel Ojeda , Boqun Feng , Gary Guo , =?iso-8859-1?Q?Bj=F6rn?= Roy Baron , Benno Lossin , Andreas Hindborg , Alice Ryhl , Trevor Gross , Danilo Krummrich , linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org Subject: Re: [PATCH] .gitignore: ignore rustc long type txt files Message-ID: <20260528203622.GA3100532@ax162> References: <20260521-rust-gitignore-long-types-txt-v1-1-5be5e6fa427c@pitsidianak.is> Precedence: bulk X-Mailing-List: linux-kbuild@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: On Thu, May 28, 2026 at 01:53:46PM +0200, Miguel Ojeda wrote: > On Thu, May 21, 2026 at 12:29 PM Manos Pitsidianakis > wrote: > > > > When rustc prints an error containing a long type that doesn't fit in a > > line, it will write the whole thing in a .txt file and print messages > > like: > > > > note: the full type name has been written to > > 'path/to/subsystem/module_name.long-type-11621316855315349594.txt > > > > Long types like core::result::Result > kernel::error::Error>: pin_init::PinInit, _> are common > > during development, so add a gitignore entry. > > > > Signed-off-by: Manos Pitsidianakis > > Cc'ing Nathan, Nicolas and Kbuild -- I considered whether deleting > these in e.g. `distclean`. They are only error artifacts, i.e. the > build system doesn't create these intentionally -- they come from the > Rust compiler in a minority of error cases (where type names are > long). > > So end users shouldn't see them anyway, so I am not sure what the policy is. I view these more like build artifacts since the messages in them are really only relevant to a specific build instance, so I would probably clean them up with 'clean' over 'mrproper' / 'distclean'. But if they are in .gitignore, I don't think it matters too much though, but it does feel like they should be cleaned up with at least 'distclean'. -- Cheers, Nathan