unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Antoine Kalmbach <ane@iki.fi>
Cc: emacs-devel@gnu.org, philipk@posteo.net
Subject: Re: Supporting git-send-email/hg email in VC
Date: Thu, 25 Aug 2022 23:35:55 -0400	[thread overview]
Message-ID: <E1oRQ8R-0007zF-6A@fencepost.gnu.org> (raw)
In-Reply-To: <848rndq2i7.fsf@iki.fi> (message from Antoine Kalmbach on Wed, 24 Aug 2022 14:56:00 +0300)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > Would it make sense for Emacs' VC to support emailing patches from
  > within Emacs? It kind of doesn't make sense that I can do mostly
  > everything in VC... but I have to jump to the command line (shell) to
  > use git-send-email.

You can already send mail inside Emacs.  It has had a feature
to edit and send messages since 1985 or so.

VC is a generic interface to version control systems.  The idea is to
make each command handles whichever version control system the files
are using.

If you'd like to implement the feature of "collect the differences
from some previous version and email them," please do not implement
it such that it is limited to one particular version control system,
or only to version control systems that have some special support.

Please implement a default method that works for all version control
systems.  The default method cannot use either git-send-email or
git-format-patch, because they (I presume) work only with git.  It
should make use of vc-diff-internal to generate the patch.

Having special code to handle the git case is ok, and it can use
git-format-patch if that works -- provided the default method makes
the feature work for other version control systems.

Use the command `compose-mail' go start setting up the email.

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  parent reply	other threads:[~2022-08-26  3:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24 11:56 Supporting git-send-email/hg email in VC Antoine Kalmbach
2022-08-24 14:43 ` Akib Azmain Turja
2022-08-24 15:11 ` Philip Kaludercic
2022-08-24 17:06 ` Stefan Monnier
2022-08-24 17:44 ` Juri Linkov
2022-08-24 21:31 ` Sam James
2022-08-25  8:36   ` Antoine Kalmbach
2022-08-25 14:47     ` Sean Whitton
2022-08-25 15:52       ` Philip Kaludercic
2022-08-25 22:04         ` Sean Whitton
2022-08-25 17:34     ` Stefan Monnier
2022-08-25 18:04       ` Philip Kaludercic
2022-08-26  7:14         ` Antoine Kalmbach
2022-08-26  7:15       ` Antoine Kalmbach
2022-08-26  3:35 ` Richard Stallman [this message]
2022-08-26  7:12   ` Antoine Kalmbach

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=E1oRQ8R-0007zF-6A@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=ane@iki.fi \
    --cc=emacs-devel@gnu.org \
    --cc=philipk@posteo.net \
    /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).