From: Stefan Kangas <stefankangas@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>, emacs-devel@gnu.org
Subject: Re: [elpa] externals/debbugs c1934c0296: New option to prefer Magit over VC
Date: Tue, 5 Sep 2023 13:30:41 -0700 [thread overview]
Message-ID: <CADwFkmkXJZ37-CP+=ArQoF=G+pbPvwBvVGVeh=5w6HdDy_GwsQ@mail.gmail.com> (raw)
In-Reply-To: <87bkeg8qcx.fsf@gmx.de>
Michael Albinus <michael.albinus@gmx.de> writes:
> Stefan Kangas <stefankangas@gmail.com> writes:
>
> Hi Stefan,
>
>> New option to prefer Magit over VC
>>
>> * debbugs-gnu.el (debbugs-gnu-apply-patch-prefers-magit): New
>> defcustom and helper function with the same name.
>> (debbugs-gnu-apply-patch): Prefer Magit to VC when above new
>> defcustom is non-nil.
>
> I believe this warrants to be mentioned in the debbugs-ug.texi manual.
Thanks, I've added it. Feel free to tweak it if you think it could be
made more clear.
> Do you plan further patches to the debbugs package?
I'm planning to teach it to use "git am" as an alternative to "patch".
I think it would work better in the Magit workflow, which would
basically be to apply the patch, and then inspect the result from the
Magit status buffer.
I'm not yet sure what to do with patches that are not formatted with
"git format-patch", though. IIUC, the VC flow using "patch" handles
that okay, but using "git am" would not.
> Shall we release a new version?
Sure, why not? Perhaps someone will find the above useful.
next prev parent reply other threads:[~2023-09-05 20:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <169385493568.10052.5329447591826946834@vcs2.savannah.gnu.org>
[not found] ` <20230904191535.F097EC04DB0@vcs2.savannah.gnu.org>
2023-09-05 17:46 ` [elpa] externals/debbugs c1934c0296: New option to prefer Magit over VC Michael Albinus
2023-09-05 20:30 ` Stefan Kangas [this message]
2023-09-06 16:29 ` Michael Albinus
2023-09-06 18:38 ` Stefan Kangas
2023-10-04 17:29 ` Michael Albinus
2023-10-04 18:43 ` Stefan Kangas
2023-10-04 19:04 ` Michael Albinus
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='CADwFkmkXJZ37-CP+=ArQoF=G+pbPvwBvVGVeh=5w6HdDy_GwsQ@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
/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).