From: Jarkko Hietaniemi <jhi@iki.fi>
To: git@vger.kernel.org
Subject: wishlist: make it possible to amend commit messages after push to remote
Date: Thu, 06 Aug 2015 20:23:02 -0400 [thread overview]
Message-ID: <55C3FA66.90805@iki.fi> (raw)
Not for the first time, and probably not for the last, I pushed a commit
upstream without adding a link for the bug report as I was meaning to.
Or it could have been...
- Simple typos.
- Broken URLs.
- The impossibility of two consecutive commits referring to each other
because the older one cannot know what the newer one will be called.
- The following morning / 5 minutes / 5 second later thinking of
an additional factoid that would've been great to have in the
commit message.
In general, I find the fact that once a commit has left the building,
it goes into your permanent record, and cannot be changed, ever, to be
very, very annoying. I get the cryptographic "sealing" with all the
preceding changes, but...
Not that I've thought this through... but couldn't there be a bunch of
"aliases" (new SHAs) for a commit? The original one being the
"master", but as/if the commit message is changed, it could get new
SHAs. Sort of separating the real data of the commit, and the metadata?
next reply other threads:[~2015-08-07 0:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 0:23 Jarkko Hietaniemi [this message]
2015-08-07 16:09 ` wishlist: make it possible to amend commit messages after push to remote Kevin Daudt
2015-08-07 17:14 ` Jarkko Hietaniemi
2015-08-07 21:02 ` Philip Oakley
2015-08-07 16:59 ` Junio C Hamano
2015-08-07 17:10 ` Jarkko Hietaniemi
2015-08-07 19:38 ` Johannes Schindelin
2015-08-07 22:50 ` Jarkko Hietaniemi
2015-08-08 9:24 ` Jeff King
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55C3FA66.90805@iki.fi \
--to=jhi@iki.fi \
--cc=git@vger.kernel.org \
/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.
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 NNTP newsgroup(s).