From: Jakub Narebski <jnareb@gmail.com>
To: "Yakov Lerner" <iler.ml@gmail.com>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: bug in git-send-mail (the 'next' branch)
Date: Tue, 18 Mar 2008 08:55:37 -0700 (PDT) [thread overview]
Message-ID: <m3abkwvxfr.fsf@localhost.localdomain> (raw)
In-Reply-To: <f36b08ee0803180652g68caa4cci21b0c59020c0fd07@mail.gmail.com>
"Yakov Lerner" <iler.ml@gmail.com> writes:
> There is a bug in git-send-mail in the 'next' branch. If first
> paragraph of the file in all indented by 1 space, and 1st line of the
> paragraph is at the first line of the file, then the whole
> paragraph disappears silently. If it's intentional, there should be a warning
> or something. And If it's *not* indented (as if it expects message
> header lines at this place), then it appears in the message body, so
> there is some inconsistency here.
I guess that this bug is in "header flowing" code; headers in email
message can span multiple lines by some use of indenting. That is
where one can search for the source of this bug...
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-03-19 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 13:52 bug in git-send-mail (the 'next' branch) Yakov Lerner
2008-03-18 15:55 ` Jakub Narebski [this message]
2008-03-19 8:03 ` Frank Lichtenheld
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=m3abkwvxfr.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=iler.ml@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.