All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Torsten Bögershausen" <tboegi@web.de>
To: "Rom Walton" <romw@romwnet.org>,
	"Toralf Förster" <toralf.foerster@gmx.de>,
	git@vger.kernel.org
Cc: boinc_dev@ssl.berkeley.edu
Subject: Re: [boinc_dev] (local ?) BOINC repo broken again -or- how to act on the CR/LF changes made upstream
Date: Sun, 14 Sep 2014 10:51:20 +0200	[thread overview]
Message-ID: <54155708.7090508@web.de> (raw)
In-Reply-To: <1BAFA9B4D550C347962F76F2E03B3BBB22C5F9@romw-mail.romwnet.org>

On 12.09.14 20:19, Rom Walton wrote:
> Try:
> git checkout -f master
> git pull origin
> 
> I committed fixes for that stuff this morning.
> 
> ----- Rom
It seems as if we added CRLF's to the repo:

od -c     html/languages/translations/hu.po | grep "\\\r"
0577300    #   #  \r  \n   #       P   r   i   v   a   t   e       m   e

I checked the latest Git, and it handles the CRLF ok.

It may be that there is a bug in the tools you are using.
Would you mind to tell us which tools and versions you used
to create commit ce97e855d0aa188757722c2 ?

  parent reply	other threads:[~2014-09-14  8:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-12 18:09 (local ?) BOINC repo broken again -or- how to act on the CR/LF changes made upstream Toralf Förster
2014-09-12 18:19 ` [boinc_dev] " Rom Walton
2014-09-12 18:32   ` Toralf Förster
2014-09-12 18:55     ` Rom Walton
2014-09-12 19:04       ` [boinc_dev] " Toralf Förster
2014-09-12 19:10         ` Rom Walton
     [not found]           ` <1BAFA9B4D550C347962F76F2E03B3BBB22C5FB-xy+Cp4waYzmnovBw3M9VzQFcV7zePqp5@public.gmane.org>
2014-09-13 14:55             ` Toralf Förster
2014-09-14  8:51   ` Torsten Bögershausen [this message]
     [not found]     ` <54155708.7090508-S0/GAf8tV78@public.gmane.org>
2014-09-14  9:04       ` Toralf Förster
2014-09-14 11:23         ` [boinc_dev] " Torsten Bögershausen
2014-09-15 21:51           ` Rom Walton

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=54155708.7090508@web.de \
    --to=tboegi@web.de \
    --cc=boinc_dev@ssl.berkeley.edu \
    --cc=git@vger.kernel.org \
    --cc=romw@romwnet.org \
    --cc=toralf.foerster@gmx.de \
    /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.