From: Ondra Medek <xmedeko@gmail.com>
To: git@vger.kernel.org
Subject: Re: gitweb showing slash r at the end of line
Date: Sun, 29 Jan 2012 23:55:40 -0800 (PST) [thread overview]
Message-ID: <1327910140526-7235866.post@n2.nabble.com> (raw)
In-Reply-To: <201201281802.44339.jnareb@gmail.com>
Hi Jakub,
I have read "SubmittingPatches". I have made a path by "git format-patch -M"
and I have though it's enough. The problem maybe was, that I had not
included "Subject: " from the result of "git format-patch -M". Next time I
will try to do it better.
I am a Git newbie, but my bare repos have "config" file and this file can
contain the "core.autocrlf" setting. So the gitweb can read it. Or what
about to have a special section [gitweb] in this config? For now, the gitweb
config files are somewhat "scattered" = "descrition", "cloneurl",
"project.list", ...
Yeah, the autodetection of mixed mode line endings could be the best
solution.
However, from my point of view a global gitweb setting would be enough for
now.
--
View this message in context: http://git.661346.n2.nabble.com/gitweb-showing-slash-r-at-the-end-of-line-tp7229895p7235866.html
Sent from the git mailing list archive at Nabble.com.
next prev parent reply other threads:[~2012-01-30 7:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 14:19 gitweb showing slash r at the end of line Ondra Medek
2012-01-27 21:35 ` Jakub Narebski
2012-01-27 23:15 ` Junio C Hamano
2012-01-28 17:02 ` Jakub Narebski
2012-01-30 7:55 ` Ondra Medek [this message]
2012-01-30 9:23 ` Jakub Narebski
2012-01-30 16:09 ` Ondra Medek
2012-02-02 20:04 ` Jakub Narebski
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1327910140526-7235866.post@n2.nabble.com \
--to=xmedeko@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).