Michal Maruska <[email protected]>
writes:
> 2/ I indeed added myself this command/function, to use the current
> line as the base for rewriting
>
> Commit msg.: from LOG start-rewriting history w/ no questions (unless C-u)
>
> (define-key magit-log-mode-map (kbd "r s") 'magit-invoke-rewrite-start)
>
> (defun magit-invoke-rewrite-start (prefix)
> "different args, to be used inside the *Log* buffer"
> (interactive "P")
> (if prefix
> (call-interactively 'magit-rewrite-start)
> (magit-rewrite-start (magit-default-rev))))
Ah.
> 3/ I see this change to the magit.texi, applied recently:
>
> + (Unless you already do so, we recommend that you don't use the
> +functionality described here. It is semi-deprecated and will be
> +removed once its unique features have been ported to the @code{git
> +rebase --interactive} workflow. Even now the latter is almost always
> +the better option.)
Aha, so `E' is old school-style, and `r *' is also semi-deprecated. So
what's the state-of-the-art interactive rebase Magit workflow then?
> I didn't know about this "git rebase --interactive" getting as usable
> as magit rewriting.
As far as I can see, `E' is basically "git rebase --interactive" with
the current log line as start, and getting the rebase buffer in
rebase-mode.
Bye,
Tassilo
--
You received this message because you are subscribed to the Google Groups
"magit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
