all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: 58383@debbugs.gnu.org
Subject: bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately
Date: Wed, 09 Nov 2022 08:28:59 +0000	[thread overview]
Message-ID: <87sfisedkk.fsf@posteo.net> (raw)
In-Reply-To: <87sfityxe8.fsf@melete.silentflame.com> (Sean Whitton's message of "Tue, 08 Nov 2022 14:00:31 -0700")

Sean Whitton <spwhitton@spwhitton.name> writes:

> Hello,
>
> On Tue 08 Nov 2022 at 08:31PM GMT, Philip Kaludercic wrote:
>
>> Sean Whitton <spwhitton@spwhitton.name> writes:
>>
>>>>> On the other hand, having a numeric prefix argument mean "send patches
>>>>> correspoding to the top N revisions of the current branch" would be very
>>>>> convenient.  Perhaps these two could be combined by using a negative
>>>>> number to mean also invert?
>>>>
>>>> This is the usual problem with numeric prefix arguments.  You don't get
>>>> that much expressivity with just an integer.
>>>>
>>>> That is why I would hesitate to assign any particular interpretation to
>>>> prefix arguments, before considering and weighing the options.
>>>
>>> Well, any other options in mind?  Varying the -N argument to
>>> git-format-patch/git-send-email is what I find myself using the most.
>>
>> The issue is finding a way for this to be expressed VC-generically.
>
> s/expressed/implemented/, right?

I meant expressed, but I don't remember what I meant ^^

So let's say implement.  What we could do is just call
`previous-revision' for the backend N times, but with what file?





  reply	other threads:[~2022-11-09  8:28 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-08 17:49 bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately Sean Whitton
2022-10-09 12:54 ` Philip Kaludercic
2022-11-04 22:21   ` Philip Kaludercic
2022-11-06 21:44     ` Sean Whitton
2022-11-06 21:49       ` Philip Kaludercic
2022-11-07 23:06   ` Sean Whitton
2022-11-08 20:31     ` Philip Kaludercic
2022-11-08 21:00       ` Sean Whitton
2022-11-09  8:28         ` Philip Kaludercic [this message]
2022-11-09 16:36           ` Sean Whitton
2022-11-09 17:46             ` Philip Kaludercic
2022-11-09 20:56               ` Sean Whitton
2022-11-10 20:14                 ` Philip Kaludercic
2022-11-11  0:07                   ` Sean Whitton
2022-11-11  6:32                     ` Philip Kaludercic
2022-11-11 20:53                       ` Sean Whitton
2022-11-13 13:56                         ` Philip Kaludercic
2022-11-13 16:06                           ` Philip Kaludercic
2022-11-13 16:35                           ` Eli Zaretskii
2022-11-13 16:45                             ` Philip Kaludercic
2022-11-13 16:52                               ` Eli Zaretskii
2022-11-13 18:17                                 ` Philip Kaludercic
2022-11-14 12:41                                   ` Eli Zaretskii
2022-11-16  0:04                                   ` Sean Whitton
2022-11-16  7:50                                     ` Philip Kaludercic
2022-11-11  7:34                     ` 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

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

  git send-email \
    --in-reply-to=87sfisedkk.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=58383@debbugs.gnu.org \
    --cc=spwhitton@spwhitton.name \
    /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 external index

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

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.