From: Jeff King <peff@peff.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Seth Falcon <sfalcon@fhcrc.org>, git@vger.kernel.org
Subject: Re: suggestion for git rebase -i
Date: Sat, 28 Jul 2007 04:45:51 -0400 [thread overview]
Message-ID: <20070728084550.GA13993@sigill.intra.peff.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0707280941380.14781@racer.site>
On Sat, Jul 28, 2007 at 09:43:15AM +0100, Johannes Schindelin wrote:
> > a file in a pre-existing editor session. I realize this is a small
> > nit, but how about renaming the file to "git-rebase-todo"?
>
> Why? This is an implementation detail, and should not concern the user.
Because if you want to setup macros or syntax highlighting specific to
editing git-rebase tempfiles, then you have to figure out somehow that
you are editing one. Using a more informative name for the tempfile
means that you can guess based on the filename.
-Peff
next prev parent reply other threads:[~2007-07-28 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-28 4:58 suggestion for git rebase -i Seth Falcon
2007-07-28 8:43 ` Johannes Schindelin
2007-07-28 8:45 ` Jeff King [this message]
2007-07-28 8:58 ` Jeff King
2007-07-28 15:52 ` Seth Falcon
2007-07-28 20:09 ` Johannes Schindelin
2007-07-28 23:11 ` Seth Falcon
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=20070728084550.GA13993@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=sfalcon@fhcrc.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).