From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb] Add .shellcheckrc
Date: Tue, 01 Sep 2026 10:25:06 -0600 [thread overview]
Message-ID: <87h5k97xct.fsf@tromey.com> (raw)
In-Reply-To: <20260831082201.3507660-1-tdevries@suse.de> (Tom de Vries's message of "Mon, 31 Aug 2026 10:22:01 +0200")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> These symlinks will be expanded to regular files in the tarballs as produced
Tom> by src-release.sh due to using "tar -h".
I thought we avoided symlinks in the source tree for some reason, I
assume Windows. Do you know?
Tom
next prev parent reply other threads:[~2026-09-01 16:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 8:22 Tom de Vries
2026-08-31 20:05 ` Simon Marchi
2026-08-31 23:04 ` Tom de Vries
2026-09-01 16:25 ` Tom Tromey [this message]
2026-09-01 16:27 ` Tom de Vries
2026-09-01 21:37 ` Tom de Vries
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=87h5k97xct.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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