From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>,
"Ryan Anderson" <ryan@michonline.com>
Subject: git-annotate dies when a patch is missing trailing newline
Date: Thu, 2 Mar 2006 13:53:21 +1300 [thread overview]
Message-ID: <46a038f90603011653l7956d5dat99d88a7da98d21b6@mail.gmail.com> (raw)
Ryan, (& list)
git-annotate is dying when a patch is missing trailing newline. There
_are_ valid situations where code files are not expected to have
trailing newlines. Just thing of that glorious programming language,
PHP.
(Ducks).
Actually, 99% of my usage of git is tracking CVS projects so this is a
bit of a problem.
I had fixed it in Johannes version, but I'm lost as to where to fix it
in the current git-annotate. Help?
martin
next reply other threads:[~2006-03-02 0:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 0:53 Martin Langhoff [this message]
2006-03-02 1:53 ` git-annotate dies when a patch is missing trailing newline Ryan Anderson
2006-03-02 2:07 ` Junio C Hamano
2006-03-02 2:23 ` Junio C Hamano
2006-03-02 3:07 ` Martin Langhoff
2006-03-02 3:37 ` Junio C Hamano
2006-03-02 4:10 ` Martin Langhoff
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=46a038f90603011653l7956d5dat99d88a7da98d21b6@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=ryan@michonline.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).