all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: 43968@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>
Subject: [bug#43968] [PATCH 0/3] Git progress report and proxy support
Date: Mon, 12 Oct 2020 22:49:57 +0200	[thread overview]
Message-ID: <20201012204957.8320-1-ludo@gnu.org> (raw)

Hello Guix!

This patch series closes two gaps:

  1. Lack of HTTP/HTTPS proxy support for Git clones/fetches as
     made by ‘guix pull’, ‘--with-branch’, etc.

  2. Lack of progress report for clones/fetches, which is a serious
     issue for big repos like that of Guix, which can take a couple
     of minutes to fetch: <https://issues.guix.gnu.org/39260>.
     This is also the first experience of ‘guix pull’ that people
     have: seemingly nothing happens during a couple of minutes.

I tested it with Guile-Git commit d418a854a3785b9ae96741f4c755517e29224197,
which should become 0.4.0 soonish.

Ludo’.

Ludovic Courtès (3):
  git: Require Guile-Git 0.3.0 or later.
  git: Display a progress bar while fetching a repo.
  git: Support HTTP and HTTPS proxies.

 configure.ac  |   5 ++
 doc/guix.texi |   4 +-
 guix/git.scm  | 140 ++++++++++++++++++++++++++++----------------------
 m4/guix.m4    |  22 ++++++++
 4 files changed, 109 insertions(+), 62 deletions(-)

-- 
2.28.0





             reply	other threads:[~2020-10-12 21:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-12 20:49 Ludovic Courtès [this message]
2020-10-12 21:09 ` [bug#43968] [PATCH 1/3] git: Require Guile-Git 0.3.0 or later Ludovic Courtès
2020-10-12 21:09   ` [bug#43968] [PATCH 2/3] git: Display a progress bar while fetching a repo Ludovic Courtès
2020-10-12 21:09   ` [bug#43968] [PATCH 3/3] git: Support HTTP and HTTPS proxies Ludovic Courtès
2020-10-22 15:12 ` bug#43968: [PATCH 0/3] Git progress report and proxy support 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

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

  git send-email \
    --in-reply-to=20201012204957.8320-1-ludo@gnu.org \
    --to=ludo@gnu.org \
    --cc=43968@debbugs.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

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.