git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: (local ?) BOINC repo broken again -or- how to act on the CR/LF changes made upstream

From
RWRom Walton <romw-egxtziwxyp1afugrpc6u6w@public.gmane.org>
Date
Sep 15, 2014, 21:51 UTC
Message-ID
<1BAFA9B4D550C347962F76F2E03B3BBB22C5FE@romw-mail.romwnet.org>
In-Reply-To
<54157AA6.7000801@web.de>
Our server runs an older version of git.
1.7.1
We are in the process of migrating to a new server which runs a more up-to-date distro.
----- Rom
-----Original Message-----
From: Torsten Bögershausen [mailto:tboegi@web.de] 
Sent: Sunday, September 14, 2014 7:23 AM
To: Toralf Förster; Torsten Bögershausen; Rom Walton; 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
On 09/14/2014 10:51 AM, Torsten Bögershausen wrote:
>> It may be that there is a bug in the tools you are using.
> I use git 2.1.0
>

The question was how the commit had been produced: Rom, what are you using ?

_______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.

Previous: Torsten Bögershausen
Message 11 of 11 in “(local ?) BOINC repo broken again -or- how to act on the CR/LF changes made upstream”
  1. Toralf FörsterSep 12, 2014
  2. Rom WaltonSep 12, 2014
  3. Toralf FörsterSep 12, 2014
  4. Rom WaltonSep 12, 2014
  5. Toralf FörsterSep 12, 2014
  6. Rom WaltonSep 12, 2014
  7. Torsten BögershausenSep 14, 2014
  8. Toralf FörsterSep 13, 2014
  9. Toralf FörsterSep 14, 2014
  10. Torsten BögershausenSep 14, 2014
  11. Rom WaltonSep 15, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.