From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 61910@debbugs.gnu.org
Subject: [bug#61910] [PATCH] git-download: Download a bare Git repository from SWH.
Date: Thu, 02 Mar 2023 18:42:48 +0100 [thread overview]
Message-ID: <87356nf3s7.fsf_-_@gmail.com> (raw)
In-Reply-To: <CAJ3okZ1kz-bL0pbaUHMUcg8YvEc1KMuS25wRgnS9h0oPL5UQgA@mail.gmail.com> (Simon Tournier's message of "Thu, 2 Mar 2023 14:50:56 +0100")
Hi,
Follow up after discussing on #swh-devel. :-)
On jeu., 02 mars 2023 at 14:50, Simon Tournier <zimon.toutoune@gmail.com> wrote:
> So the question is how to know which files require CRLF and which not?
>
> From my understanding, this information is provided by:
>
> $ cat hidapi.guix/.gitattributes
> * text=auto
>
> *.sln text eol=crlf
> *.vcproj text eol=crlf
>
> bootstrap text eol=lf
> configure.ac text eol=lf
Yeah, we could parse this file. It is not that hard but I am not so
much interested right now for implementing such.
> As zack pointed yesterday, well that what I understood or
> misunderstood, it is related to "smudge" filters [1].
No, it is not “smudge”. These attributes are much simpler than
smudge/clean filters – well they are scary!
> Kidding aside, I agree that relying on Guile-Git would mean being less
> "fragile". Hum, somehow this asks about the size of the binary seed
> for bootstrapping.
After some quick look, Guile-Git provides some plumbing and here it is
more about porcelain. Well, I do not know how it could be implemented
with Guile-Git.
> About low-level 'git' command, maybe the same could be achieved
> without "git init" + "git add" + "git commit". Well, my gitology is
> not enough skilled. :-)
Asking on #swh-devel, vlorentz confirmed using something similar.
Quoting: « I looked at git's normalization-related test cases; but they
all use git-add »
Therefore, I guess that’s probably the best tradeoff for now.
Well, I am going to run more tests.
Cheers,
simon
next prev parent reply other threads:[~2023-03-02 19:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 9:12 [bug#61910] [PATCH] git-download: Download a bare Git repository from SWH Ludovic Courtès
2023-03-02 10:30 ` Simon Tournier
2023-03-02 12:05 ` [bug#61910] [PATCH v2] git-download: Apply CR/LF to " Simon Tournier
2023-03-02 13:15 ` [bug#61910] [PATCH] git-download: Download a bare " Ludovic Courtès
2023-03-02 13:50 ` Simon Tournier
2023-03-02 17:42 ` Simon Tournier [this message]
2023-03-03 11:12 ` Ludovic Courtès
2023-03-03 13:27 ` bug#61910: " Ludovic Courtès
2023-03-03 18:52 ` [bug#61910] " Simon Tournier
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=87356nf3s7.fsf_-_@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=61910@debbugs.gnu.org \
--cc=ludo@gnu.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://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).