From: Matt <matt@excalamus.com>
To: "Max Nikulin" <manikulin@gmail.com>
Cc: "emacs-orgmode" <emacs-orgmode@gnu.org>
Subject: Re: How to properly attribute authorship with Git (was Re: [PATCH] lisp/ob-shell.el: Also override explicit-shell-file-name)
Date: Sun, 17 Mar 2024 18:32:03 +0100 [thread overview]
Message-ID: <18e4d787582.fd03b1d5688934.8119065120295524965@excalamus.com> (raw)
In-Reply-To: <ut75k8$15od$2@ciao.gmane.io>
---- On Sun, 17 Mar 2024 17:26:48 +0100 Max Nikulin wrote ---
> On 17/03/2024 20:42, Matt wrote:
> > ---- On Sun, 17 Mar 2024 11:31:00 +0100 Ihor Radchenko wrote ---
> > >
> > > (1) revert the commit; (2) re-apply the
> > > commit version with the correct author attribution.
> >
> > Done.
> >
> > 1. git revert
> > 2. make changes (e.g. emacs followed by *type-type-type* or some incantation of 'git apply' or 'git am')
> > 3. git commit --author "Arthur Author "
>
> In this particular case "git am" works fine and no explicit "git commit"
> is necessary.
Thank you for taking the time to verify the patch formatting. Sounds like a PEBKAC. I'll look into fixing it :)
--
Matt Trzcinski
Emacs Org contributor (ob-shell)
Learn more about Org mode at https://orgmode.org
Support Org development at https://liberapay.com/org-mode
prev parent reply other threads:[~2024-03-17 17:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 5:12 [PATCH] lisp/ob-shell.el: Also override explicit-shell-file-name Aaron L. Zeng
2024-03-11 19:16 ` Matt
2024-03-12 13:29 ` Ihor Radchenko
2024-03-15 21:38 ` Matt
2024-03-15 22:08 ` Aaron Zeng
2024-03-16 10:11 ` Ihor Radchenko
2024-03-17 9:06 ` How to properly attribute authorship with Git (was Re: [PATCH] lisp/ob-shell.el: Also override explicit-shell-file-name) Matt
2024-03-17 10:31 ` Ihor Radchenko
2024-03-17 13:42 ` Matt
2024-03-17 14:38 ` Ihor Radchenko
2024-03-17 16:26 ` Max Nikulin
2024-03-17 17:32 ` Matt [this message]
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18e4d787582.fd03b1d5688934.8119065120295524965@excalamus.com \
--to=matt@excalamus.com \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.com \
/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/org-mode.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).