| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This bases the implementation of git-email-patch-send off the magit
upstream magit-patch-create. This makes it more intuitive since it's
not defining a different way to work with patches.
This means by default you'll be presented with a revision range
prompt with the expectation that you would use a range like
upstream/master..master or something to calculate the patches to be
created. This on the surface seems more complicated than just
choosing a starting point, but it's more powerful and simple range
selection can be done interactively using the log buffer.
If you want to create a single patch thing can be done by pressing
`C-SPC` in the magit log buffer on a single commit then proceeding
with `W c s` or you can create any arbitrary interactive range via
`C-SPC` and navigating around the log.
Signed-off-by: Russell Sim <russell.sim@gmail.com>
|
|
|
|
|
|
|
|
| |
Without this strings with whitespaces would cause ‘git format-patch’
to fail.
* git-email-magit.el (git-email--escape-string): New function.
(git-email-magit-patch-send): Use it.
|
|
|
|
|
|
|
|
|
| |
Spaces >> tabs.
* git-email.el: Untabify.
* git-email-gnus.el: Likewise.
* git-email-magit.el: Likewise.
* git-email-notmuch.el: Likewise.
|
|
|
|
|
|
| |
Use "all contributors" rather than a name.
Signed-off-by: Xinglu Chen <public@yoctocell.xyz>
|
|
|
|
| |
* git-email-magit.el: Add transient to "Package-Requires" field.
|
|
|
|
|
|
| |
This is what I get when I am lazy.
* git-email-magit.el: Fix typos git-email-notmuch -> git-email-magit.
|
| |
|
| |
|
|
|
|
|
| |
This brings up a log buffer where the user the select a commit,
similar to when doing an interactive rebase.
|
|
This will extend the `magit-patch-create' transient prefix with a
second action -- "Send patch".
|