unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Arthur Miller <arthur.miller@live.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Giap Tran <txgvnn@gmail.com>,
	49980@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#49980: 28.0.50; [PATCH] Should we have project-save-buffers?
Date: Mon, 16 Aug 2021 15:22:36 +0200	[thread overview]
Message-ID: <AM9PR09MB4977CA5B4E2921373591BE7996FD9@AM9PR09MB4977.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <5965bcdd-d09a-0fef-18ba-c75de3200845@yandex.ru> (Dmitry Gutov's message of "Mon, 16 Aug 2021 06:06:23 +0300")

Dmitry Gutov <dgutov@yandex.ru> writes:

> On 16.08.2021 04:19, Arthur Miller wrote:
>> What do you think about checking out, between multiple different
>> branches? Switching two branches back and forth is no brainer, it should
>> always work fine, but switching multiple branches can lead to mess since
>> stashes are applied automatically. Any good strategy to automate this
>> case?
>
> I don't know. You're automating a case I have been handling manually (and hadn't
> been bothered by that, thus far).
>
> You will most likely encounter some edge cases where the automation breaks, but
> it's hard to predict those in advance.
>
>> Honestly, I don't see much difference than doing it manually, but I am a
>> bit affraid of auto applying stashes.
>
> As long as they're named ones (and thus you won't miss and accidentally pop an
> unrelated one), this should work fine.

Yes, they are named ones. I am trying to think out what could get
messed, but since everything is stashed away on every checkout, so I
don't think it should be more dangerous than doing it manually. Don't
time will tell me, I am using this myself, so I guess I'll notice.

thanks for the feedback





  reply	other threads:[~2021-08-16 13:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-10  9:23 bug#49980: 28.0.50; [PATCH] Should we have project-save-buffers? Giap Tran
2021-08-11  6:52 ` Juri Linkov
2021-08-11  7:38   ` Giap Tran
2021-08-11 12:23   ` Dmitry Gutov
2021-08-12  7:55     ` Juri Linkov
2021-08-13  2:06       ` Dmitry Gutov
2021-08-13  7:12         ` Juri Linkov
2021-08-13  9:39         ` Arthur Miller
2021-08-13 16:05           ` Juri Linkov
2021-08-13 17:22             ` Arthur Miller
2021-08-14  2:25             ` Arthur Miller
2021-08-15  8:32               ` Juri Linkov
2021-08-15 10:44                 ` Arthur Miller
2021-08-13 23:54           ` Dmitry Gutov
2021-08-14  2:46             ` Arthur Miller
2021-08-16  0:37               ` Dmitry Gutov
2021-08-16  1:19                 ` Arthur Miller
2021-08-16  3:06                   ` Dmitry Gutov
2021-08-16 13:22                     ` Arthur Miller [this message]
2021-08-11 12:22 ` Dmitry Gutov
2021-08-11 13:40   ` Giap Tran
2021-08-13  2:11     ` Dmitry Gutov

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AM9PR09MB4977CA5B4E2921373591BE7996FD9@AM9PR09MB4977.eurprd09.prod.outlook.com \
    --to=arthur.miller@live.com \
    --cc=49980@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=juri@linkov.net \
    --cc=txgvnn@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).