From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: manuel.uberti@inventati.org, 51897@debbugs.gnu.org
Subject: bug#51897: 29.0.50; keymap-global-unset cannot unset C-x C-z
Date: Wed, 17 Nov 2021 15:59:38 +0200 [thread overview]
Message-ID: <83k0h6zxv9.fsf@gnu.org> (raw)
In-Reply-To: <87ilwrp69v.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 17 Nov 2021 08:53:32 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 51897@debbugs.gnu.org, manuel.uberti@inventati.org
> Date: Wed, 17 Nov 2021 08:53:32 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Are you using "C-x v v", perhaps? At some point in the past I
> > proposed to teach "C-x v v" to suggest a push after commit, or even
> > optionally do a push without asking, given some user customization.
> > But that idea was shot down for reasons I still don't understand.
> > I think keeping push out of the "C-x v v" cycle makes that command
> > much less useful nowadays.
>
> I do see the objection from a standpoint of "well, a commit and a push
> are two totally separate operations" Git standpoint
I didn't suggest to do them both in one go, I suggested that invoking
"C-x v v" _after_ the one that committed a changeset will either push
or offer pushing as one of a small number of possible actions.
> After thinking about it a bit more, I'm not quite sure what I'd prefer
> myself. It's not uncommon for me that I remember something after I've
> hit `C-x v v' (like adding Copyright-paperwork-exempt: yes to the commit
> message), and having this be a two step operation helps with that,
> because I can just back out the commit and try again, which I can't if
> I've already pushed.
What is reasonable after a commit? Either (a) show or (b) push or (c)
another commit or (d) pull. So why not ask the user which one of
these would he/she want to do? We could even try to be smart about
that: for example, if the clone is ahead of upstream, push might be
the moist reasonable possibility.
What does "C-x v v" do today after push? If the tree is clean,
nothing useful. So what are we going to lose?
> But on the other hand, I forget to push so often that it's ridiculous.
> I think one of the contributing factors is that it just takes a while --
> I mean, I have to pull first, wait for it to finish, and then push.
For that reason, I never pull before pushing, unless push tells me I
must.
next prev parent reply other threads:[~2021-11-17 13:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 18:26 bug#51897: 29.0.50; keymap-global-unset cannot unset C-x C-z Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-16 18:42 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-16 18:42 ` Lars Ingebrigtsen
2021-11-16 18:43 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-16 18:48 ` Eli Zaretskii
2021-11-16 19:02 ` Lars Ingebrigtsen
2021-11-16 19:19 ` Eli Zaretskii
2021-11-17 7:53 ` Lars Ingebrigtsen
2021-11-17 8:17 ` Juri Linkov
2021-11-18 9:17 ` Lars Ingebrigtsen
2021-11-17 13:59 ` Eli Zaretskii [this message]
2021-11-18 9:19 ` Lars Ingebrigtsen
2021-11-18 11:07 ` Eli Zaretskii
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=83k0h6zxv9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51897@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=manuel.uberti@inventati.org \
/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).