unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: "Grigory Shepelev" <shegeley@gmail.com>,
	"Ludovic Courtès" <ludo@gnu.org>
Cc: 52801@debbugs.gnu.org
Subject: bug#52801: Guile misbehaves in case of escapes and carriage returns, sometimes breaking "guix pull"
Date: Sun, 30 Jan 2022 22:06:29 +0100	[thread overview]
Message-ID: <982577c012cb2c3882821e9b8e19968b5b9f4936.camel@telenet.be> (raw)
In-Reply-To: <CAGJuR-74nJiEFeSMPG-V6ULXgdt__xmMKjLL_wTunhbBpLezvQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 509 bytes --]

Grigory Shepelev schreef op zo 30-01-2022 om 22:45 [+0300]:
> Seems like the problem was in my .gitconfig file where "autocrlf =
> true". I set it to "false", and cleared the cache. Then the "guix
> pull" started to work as expected. 

According to
<https://github.com/libgit2/libgit2/blob/HEAD/include/git2/clone.h#L111>
and <https://libgit2.org/libgit2/#HEAD/type/git_checkout_options>,
we can tell libgit to not do CRLF conversion, which would make (guix git)
more robust.

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  parent reply	other threads:[~2022-01-30 21:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-26 10:14 bug#52801: Bug report Grigory Shepelev
2021-12-26 11:22 ` bug#52801: Guile inconsistently misbehaves in case of escapes and carriage returns, breaking "guix pull" Maxime Devos
2022-01-30 17:52 ` bug#52801: Guile misbehaves in case of escapes and carriage returns, sometimes " Ludovic Courtès
2022-01-30 19:45   ` Grigory Shepelev
2022-01-30 19:47     ` Grigory Shepelev
2022-01-30 21:06     ` Maxime Devos [this message]
2022-01-31 12:48       ` Grigory Shepelev
2022-01-31 13:20         ` Maxime Devos
2022-02-01  8:48       ` Ludovic Courtès

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: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=982577c012cb2c3882821e9b8e19968b5b9f4936.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=52801@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=shegeley@gmail.com \
    /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://git.savannah.gnu.org/cgit/guix.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).