git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Antonio Ospite <ospite@studenti.unina.it>
Cc: git@vger.kernel.org
Subject: Re: Feature idea: git rebase --exec $CMD
Date: Sun, 06 May 2012 12:03:49 +0200	[thread overview]
Message-ID: <vpqobq1mxru.fsf@bauges.imag.fr> (raw)
In-Reply-To: <20120505132650.637c4e06086654e0dbf641fc@studenti.unina.it> (Antonio Ospite's message of "Sat, 5 May 2012 13:26:50 +0200")

Antonio Ospite <ospite@studenti.unina.it> writes:

> Maybe this -x option should conflict with -i to simplify its "execute
> the command after each commit" semantics (what if it is combined with -i
> and 'x/exec' lines?).

Actually, implementation-wise, it's simpler to have '-x' imply '-i', and
suggest a todo-list containing 'x' lines. Then, the code would simply
have to add these "x whatever" lines, and let the
"git-rebase--interactive.sh" mechanics do the job. That would show the
"x whatever" lines to the user, but that can be seen as added value,
since it gives an opportunity to the user to remove or edit some of them
if needed.

I'm not familiar with the code behind non-interactive rebase, but it
doesn't seem to use the same todo-list at all. Maybe the sequencer would
help, I don't know.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

  parent reply	other threads:[~2012-05-06 10:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-05 11:26 Feature idea: git rebase --exec $CMD Antonio Ospite
2012-05-05 11:54 ` Felipe Contreras
2012-05-06 10:03 ` Matthieu Moy [this message]
2012-05-06 10:44   ` Antonio Ospite
2012-05-06 12:26   ` Jeff King
2012-05-10  8:28 ` Matthieu Moy
2012-05-23 15:12 ` dag
2012-05-23 15:41   ` Matthieu Moy
2012-05-23 15:50     ` dag

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vpqobq1mxru.fsf@bauges.imag.fr \
    --to=matthieu.moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=ospite@studenti.unina.it \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).