From: Jan Hudec <bulb@ucw.cz>
To: git@vger.kernel.org
Subject: [Qgit RFC] commit --amend
Date: Sun, 10 Jun 2007 17:08:39 +0200 [thread overview]
Message-ID: <20070610150839.GG4084@efreet.light.src> (raw)
[-- Attachment #1: Type: text/plain, Size: 1554 bytes --]
Hello,
I am thinking about adding commit --amend support to Qgit.
However I see three ways to do it, so I'd like to ask whether anybody knows
some reason why any of them is better or worse, which I don't:
- Add a button for "Amend". This would fit with what is there currently,
because with stgit it has buttons "New patch" and "Add to top" (refresh),
which correspond exactly to core git's "commit" and "commit --amend"
respectively.
Disadvantage (for current approach too) is, that when amending (resp.
refreshing) the previous commit message is not there to be edited.
- Add a radio button the way git-gui does. Switching the button to "amend"
would load the previous commit message.
This would be more invasive change, but it would allow editing the commit
message when amending/refreshing. I fear it will be more user-error-prone
too, though.
- Add a separate action to the menu. This action would take over the refresh
(Add to top) operation when using stgit.
I believe this has lower risk of user errors than the previous option. It
also has the advantage, that I don't have to touch the disabling logic for
the commit action. Amending last commit is always possible, even if there
are no changes, because you might want to edit the message (eg. if you
forget to sign-off or forget to mention some change or something).
I'll try doing the first option now, unless somebody persuades me that it's
a nonsense.
--
Jan 'Bulb' Hudec <bulb@ucw.cz>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-06-10 15:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-10 15:08 Jan Hudec [this message]
2007-06-10 22:10 ` [Qgit RFC] commit --amend Marco Costalba
2007-06-11 4:42 ` Jan Hudec
2007-06-11 5:24 ` Marco Costalba
2007-06-11 5:45 ` Marco Costalba
2007-07-01 12:26 ` Jan Hudec
2007-07-01 16:09 ` Marco Costalba
2007-07-02 18:03 ` Jan Hudec
2007-07-04 5:10 ` Junio C Hamano
2007-07-04 12:44 ` Marco Costalba
2007-07-04 18:28 ` Jan Hudec
2007-07-04 19:51 ` Junio C Hamano
2007-07-06 7:54 ` Marco Costalba
2007-07-05 18:54 ` Jan Hudec
2007-07-06 8:12 ` Marco Costalba
2007-07-08 13:38 ` Jan Hudec
2007-07-08 13:49 ` Marco Costalba
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=20070610150839.GG4084@efreet.light.src \
--to=bulb@ucw.cz \
--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).