From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitfaq: document using stash import/export to sync working tree
Date: Fri, 09 Jan 2026 17:56:00 -0800 [thread overview]
Message-ID: <xmqqo6n2temn.fsf@gitster.g> (raw)
In-Reply-To: <aWFg_VUZH5_ZqTix@fruit.crustytoothpaste.net> (brian m. carlson's message of "Fri, 9 Jan 2026 20:11:41 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> On 2026-01-09 at 14:32:40, Junio C Hamano wrote:
>> "brian m. carlson" <sandals@crustytoothpaste.net> writes:
>>
>> > Git 2.51 learned how to import and export stashes. This is a
>> > secure and robust way to transfer working tree states across machines
>>
>> Here "secure" in "secure and robust" triggered my "huh?" sensor. It
>> is a robust way, but is there something particularly "secure" about
>> it, other than "it is less likely to break your repository" in the
>> sense that is already covered by "robust".
>
> We know that sharing a working tree with different users is not secure
> because people can have things like hooks or config options that execute
> arbitrary code. Transferring stashes doesn't have that downside.
Ah, I wasn't thinking about two different people transferring
repositories. Using rsync may have that downside.
prev parent reply other threads:[~2026-01-10 1:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 1:46 [PATCH] gitfaq: document using stash import/export to sync working tree brian m. carlson
2026-01-09 14:32 ` Junio C Hamano
2026-01-09 20:11 ` brian m. carlson
2026-01-10 1:56 ` Junio C Hamano [this message]
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=xmqqo6n2temn.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.