From: Sam Hocevar <sam@zoy.org>
To: git@vger.kernel.org
Subject: msysgit corrupting commit messages?
Date: Fri, 6 Mar 2009 18:11:17 +0100 [thread overview]
Message-ID: <20090306171117.GD12880@zoy.org> (raw)
In-Reply-To: <CYOA8Q1cpfGtE1Pp6_ETXfSJevKv9ADmYIuq6_whU0qskk289fiiUw@cipher.nrlssc.navy.mil>
On Fri, Mar 06, 2009, Brandon Casey wrote:
> I get the impression that you do not intend for the comments above to be
> part of the commit message. If that is true, then they should be placed
> further down after the '---' and before the diff-stat, or in some other
> way partitioned from the commit message (maybe using --->8--- notation).
> Otherwise they will _become_ part of the commit message if Junio applies
> this patch as-is.
Okay. I'm definitely having a problem with git on MSYS. Is anyone
else seeing it butcher commits it exports? They appear fine in git log
or git log -p, but not in git format-patch. I've never had the problem
on a Linux system.
--
Sam.
next prev parent reply other threads:[~2009-03-06 17:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 15:53 [PATCH] git-p4: remove unnecessary semicolons at end of lines Sam Hocevar
2009-03-06 16:55 ` Brandon Casey
2009-03-06 17:11 ` Sam Hocevar [this message]
2009-03-07 2:48 ` msysgit corrupting commit messages? Johannes Schindelin
2009-03-07 12:26 ` [PATCH v2] git-p4: remove unnecessary semicolons at end of lines Sam Hocevar
-- strict thread matches above, loose matches on Subject: below --
2009-03-04 21:54 [PATCH] git-p4: improve performance with large files Sam Hocevar
2009-03-04 23:05 ` thestar
2009-03-05 17:23 ` Sam Hocevar
2009-03-06 0:01 ` thestar
2009-03-06 1:14 ` Junio C Hamano
2009-03-06 1:25 ` Han-Wen Nienhuys
2009-03-06 8:53 ` Sam Hocevar
2009-03-06 9:42 ` Junio C Hamano
2009-03-06 10:13 ` [PATCH v4] " Sam Hocevar
2009-03-07 12:25 ` [PATCH v5] git-p4: improve performance when importing huge files by reducing the number of string concatenations while constraining memory usage Sam Hocevar
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=20090306171117.GD12880@zoy.org \
--to=sam@zoy.org \
--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).