From: Yue Lin Ho <yuelinho777@gmail.com>
To: git@vger.kernel.org
Subject: Re: The different EOL behavior between libgit2-based software and official Git
Date: Fri, 20 Jun 2014 01:44:31 -0700 (PDT) [thread overview]
Message-ID: <1403253871592-7613801.post@n2.nabble.com> (raw)
In-Reply-To: <53A3DB01.7090904@web.de>
Wow!
P.S.
A note:
libgit2 just has a PR that try to be identical with official git 2.0.0.
See https://github.com/libgit2/libgit2/pull/2432
--
View this message in context: http://git.661346.n2.nabble.com/The-different-EOL-behavior-between-libgit2-based-software-and-official-Git-tp7613670p7613801.html
Sent from the git mailing list archive at Nabble.com.
prev parent reply other threads:[~2014-06-20 8:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 2:59 The different EOL behavior between libgit2-based software and official Git Yue Lin Ho
2014-06-19 6:39 ` Torsten Bögershausen
2014-06-19 7:25 ` Yue Lin Ho
2014-06-20 6:56 ` Torsten Bögershausen
2014-06-20 8:30 ` Yue Lin Ho
2014-06-20 10:33 ` [msysGit] " Torsten Bögershausen
2014-06-20 16:33 ` Junio C Hamano
2014-06-22 6:46 ` [msysGit] " Torsten Bögershausen
2014-06-23 17:29 ` Junio C Hamano
2014-06-20 8:44 ` Yue Lin Ho [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=1403253871592-7613801.post@n2.nabble.com \
--to=yuelinho777@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).