All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Hanan Arshad <hananarshad619@gmail.com>
Cc: j6t@kdbg.org,  git@vger.kernel.org,  sandals@crustytoothpaste.net
Subject: Re: [RFC] git stash: add porcelain for sharing stashes through remotes
Date: Mon, 05 Oct 2026 08:25:38 -0700	[thread overview]
Message-ID: <xmqqzewsmaod.fsf@gitster.g> (raw)
In-Reply-To: <CAKPibBwjRSb5cXd2iWo8bbYby1odcXNazEg-D9hcqbehrR6g3w@mail.gmail.com> (Hanan Arshad's message of "Mon, 5 Oct 2026 02:06:36 -0700")

Hanan Arshad <hananarshad619@gmail.com> writes:

> The narrower proposal I am considering now is only around the parts of
> the temporary handoff workflow that are less convenient today:
>
> - discovering available remote stash refs,
> - fetching one and storing it as a normal local stash entry,
> - removing the remote ref when it is no longer needed.

FWIW, I agree with j6t.  Quoting the part you left at the bottom of
your message (by the way, please do not top-post on this list.  You
quote what others said first, and then you write your response below
that):

>> So, IMHO, there is zero reason to upgrade stashes so that they can
>> achieve the exact same thing that we can already do with branches.
>>
>> (Hence, if indeed you do share your half-finsihed work ten times a day,
>> then, please, by all means, use the right tool for the task: put your
>> work on a branch, not in a stash.)

All of the three you listed (discovery, transfer, clean-up) become
easier to work with if you used branches, branches have always had
good support for these three (and other) operations, and I do not
see a good reason to add a parallel support to do something similar.


  reply	other threads:[~2026-10-05 15:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28 14:27 [RFC] git stash: add porcelain for sharing stashes through remotes Hanan Arshad
2026-09-29 22:19 ` brian m. carlson
2026-10-05  5:53   ` Hanan Arshad
2026-10-05  7:47     ` Johannes Sixt
2026-10-05  8:03       ` Hanan Arshad
2026-10-05  8:21         ` Johannes Sixt
2026-10-05  9:06           ` Hanan Arshad
2026-10-05 15:25             ` Junio C Hamano [this message]
2026-10-07  6:31               ` Hanan Arshad
2026-10-07 10:36                 ` Johannes Sixt
  -- strict thread matches above, loose matches on Subject: below --
2026-10-01  8:53 Hanan Arshad
2026-10-01 22:02 ` D. Ben Knoble
2026-10-01 22:16   ` Junio C Hamano

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=xmqqzewsmaod.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=hananarshad619@gmail.com \
    --cc=j6t@kdbg.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.