From: Jarkko Hietaniemi <jhi@iki.fi>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: wishlist: make it possible to amend commit messages after push to remote
Date: Fri, 07 Aug 2015 13:10:23 -0400 [thread overview]
Message-ID: <55C4E67F.7050109@iki.fi> (raw)
In-Reply-To: <xmqqd1yzyqzq.fsf@gitster.dls.corp.google.com>
On Friday-201508-07 12:59, Junio C Hamano wrote:
> You need to learn to consider the act of publishing as casting
your work in stone to give other people solid foundation to build
on.
> ...
> If you really "get" it, you wouldn't be complaining about the
> "impossibility" part;-)
I wasn't suggesting taking away the original SHA.
But to be honest, I wasn't expecting a miracle cure. I guess the core
of my gripe is just that: how the commit message is part of the SHA.
But that's part of the SHA and genome of git. In other words:
"sorry dude, you are out of luck".
next prev parent reply other threads:[~2015-08-07 17:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 0:23 wishlist: make it possible to amend commit messages after push to remote Jarkko Hietaniemi
2015-08-07 16:09 ` 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 [this message]
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=55C4E67F.7050109@iki.fi \
--to=jhi@iki.fi \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).