From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Subject: Re: Reordering lines in "git-rebase -i" task sheet
Date: Mon, 26 Nov 2007 13:14:02 +0000 [thread overview]
Message-ID: <fiegqq$kq5$1@ger.gmane.org> (raw)
In-Reply-To: fi64ge$u1g$1@ger.gmane.org
Andy Parkins wrote:
> I'm not convinced that this is a great idea.
I've just tried it and (for me) I don't like it.
- It's now harder to find the commits I want to edit, the cursor still
doesn't start in the right place, but now I can't get to the right place
quickly (the right place being the bottom of the list) because the
interesting bits are neither at the top nor at the bottom
- vim no longer automatically loads a reasonable syntax highlighting mode
making the comment lines appear the same as the pick lines.
- On a long rebase list the important message explaining what I'm looking
at isn't on screen.
Andy
--
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com
prev parent reply other threads:[~2007-11-26 13:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 9:21 Reordering lines in "git-rebase -i" task sheet Junio C Hamano
2007-11-22 11:15 ` [PATCH] rebase -i: move help to end of todo file Johannes Schindelin
2007-11-22 11:41 ` [PATCH] Adjust t3404 to ignore empty lines in the " Johannes Schindelin
2007-11-22 11:46 ` [PATCH] rebase -i: move help to end of " Junio C Hamano
2007-11-22 12:30 ` Johannes Schindelin
2007-11-22 12:31 ` Jeff King
2007-11-22 11:18 ` [PATCH] rebase -i: give rerere a chance Johannes Schindelin
2007-11-29 0:17 ` Junio C Hamano
2007-11-29 0:22 ` Johannes Schindelin
2007-11-29 9:59 ` David Kastrup
2007-11-22 19:25 ` Reordering lines in "git-rebase -i" task sheet David Brown
2007-11-22 22:11 ` Johannes Schindelin
2007-11-23 8:54 ` Andy Parkins
2007-11-26 13:14 ` Andy Parkins [this message]
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='fiegqq$kq5$1@ger.gmane.org' \
--to=andyparkins@gmail.com \
--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).