From: Jan Hudec <bulb@ucw.cz>
To: Marco Costalba <mcostalba@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [Qgit RFC] commit --amend
Date: Mon, 11 Jun 2007 06:42:58 +0200 [thread overview]
Message-ID: <20070611044258.GJ4084@efreet.light.src> (raw)
In-Reply-To: <e5bfff550706101510x6d685944ja70c9d9dbb3668f6@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2536 bytes --]
On Mon, Jun 11, 2007 at 00:10:20 +0200, Marco Costalba wrote:
> On 6/10/07, Jan Hudec <bulb@ucw.cz> wrote:
> >Hello,
> >
> >I am thinking about adding commit --amend support to Qgit.
> >
>
> Good!
>
> > - 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).
> >
>
> Yes. But amending is an option of commit (also in git) so probably the
> amend action will fire the commit dialog anyway and we are back to
> previous situation. The only advantage is that we can load the message
> of the tip revision as default instead of git-status output as the
> current.
>
>
> >I'll try doing the first option now, unless somebody persuades me that it's
> >a nonsense.
> >
>
> I think it's the best: 'Sync' button is very seldom used (I think I've
> never used it but for testing that it works) and updating the index is
> something very plumbing anyway.
>
> What we could add is another button 'Load prev msg' to do what it
> says, so we would end up with 5 buttons:
>
> - Settings /Cancel/ Load prev msg / Amend /Commit
>
> I don't see a reason to set 'Load prev msg' as a check button, you may
> want to reload the prev msg as many times as you need, (re)clicking
> everytime on the button, also for a normal commit where as example you
> want to keep the header or part of the subject of the previous
> revision.
I think it would be somewhat complicated unfortunately :-(. The loading of
previous message should be really tied to whether you are about to
amend/refresh or to commit/add new. In this respect this would actually match
the command-line interface, because you say whether you want to amend
*before* you edit the message.
So I am now inclined more to the separate action and trying to go that way.
But the difference between the variants would not be that big.
> Please let me know if and where you find something obscure/messy with
> the code, I will be happy to help you.
I think I mostly understood it now. Thank you.
--
Jan 'Bulb' Hudec <bulb@ucw.cz>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-11 4:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-10 15:08 [Qgit RFC] commit --amend Jan Hudec
2007-06-10 22:10 ` Marco Costalba
2007-06-11 4:42 ` Jan Hudec [this message]
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=20070611044258.GJ4084@efreet.light.src \
--to=bulb@ucw.cz \
--cc=git@vger.kernel.org \
--cc=mcostalba@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.
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).