[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separate
From: |
Sean Whitton |
Subject: |
bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately |
Date: |
Thu, 10 Nov 2022 17:07:03 -0700 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Hello,
On Thu 10 Nov 2022 at 08:14PM GMT, Philip Kaludercic wrote:
> Sean Whitton <spwhitton@spwhitton.name> writes:
>
>> Hello,
>>
>> On Wed 09 Nov 2022 at 05:46PM GMT, Philip Kaludercic wrote:
>>
>>> The critical edge-case here is what happens when branches are merged.
>>> Do you pick a random branch or collect all the patches. Or do you raise
>>> an error, but then how do you detect that vc-generically.
>>
>> Typically you wouldn't want to format patches across a merge, so I would
>> suggest raising an error.
>
> And this is something I don't think can be /expressed/ using vc, because
> while I can collect a number of revisions using `previous-revision',
> there is no general way to verify if a commit is a merge commit.
Can we do that part on a VCS-by-VCS basis? Default to just calling
previous-revision and hoping for the best, but giving vc-git.el a chance
to raise an error.
--
Sean Whitton
- bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately, (continued)
- bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately, Sean Whitton, 2022/11/06
- bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately, Sean Whitton, 2022/11/07
- bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately, Philip Kaludercic, 2022/11/08
- bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately, Sean Whitton, 2022/11/08
- bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately, Philip Kaludercic, 2022/11/09
- bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately, Sean Whitton, 2022/11/09
- bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately, Philip Kaludercic, 2022/11/09
- bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately, Sean Whitton, 2022/11/09
- bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately, Philip Kaludercic, 2022/11/10
- bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately,
Sean Whitton <=
- bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately, Philip Kaludercic, 2022/11/11
- bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately, Sean Whitton, 2022/11/11
- bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately, Philip Kaludercic, 2022/11/13
- bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately, Philip Kaludercic, 2022/11/13
- bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately, Eli Zaretskii, 2022/11/13
- bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately, Philip Kaludercic, 2022/11/13
- bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately, Eli Zaretskii, 2022/11/13
- bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately, Philip Kaludercic, 2022/11/13
- bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately, Eli Zaretskii, 2022/11/14
- bug#58383: 29.0.50; Make it easier to invert vc-prepare-patches-separately, Sean Whitton, 2022/11/15