From: "Philip Oakley" <philipoakley@iee.org>
To: <jhi@iki.fi>, "Kevin Daudt" <me@ikke.info>
Cc: <git@vger.kernel.org>
Subject: Re: wishlist: make it possible to amend commit messages after push to remote
Date: Fri, 7 Aug 2015 22:02:12 +0100 [thread overview]
Message-ID: <43BA4A09C14A43DEB23F4F14C2279A30@PhilipOakley> (raw)
In-Reply-To: 55C4E77C.8070402@iki.fi
From: "Jarkko Hietaniemi" <jhi@iki.fi>
> Thanks (also to Jacob Keller), the git-notes might work in some cases.
> But it's obviously a pasted-on solution, requiring a different usage,
> e.g. "git log --notes", and whatever other UIs do with it.
>
>> One more thing, if you know that no one has fetched the branch you
>> just
>> pushed yet, you can amend the commit and force-push it without any
>> problems (I'd sugget using --force-with-lease).
>
> In my particular case, not going to work, multiple CI engines jump
> hungry at every commit.
Sound like you need an intermediate repo (similar in style to a personal
github repo) between your personal machine and the CIs so that you get
the chance to do those rebases/amendments, before you finally push to
the CI.
It's almost the same human psychology issue as realizing what to do
_after_ sending an email asking for help (and wanting to recall the
email...).
To me, part of the sucess of a DVCS is having that extra layer where
control has been distributed to you, rather than control still being
with 'them'.
</bikeshedding>
--
Philip
next prev parent reply other threads:[~2015-08-07 21:01 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 [this message]
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=43BA4A09C14A43DEB23F4F14C2279A30@PhilipOakley \
--to=philipoakley@iee.org \
--cc=git@vger.kernel.org \
--cc=jhi@iki.fi \
--cc=me@ikke.info \
/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).