bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Collin Funk <collin.funk1@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>,
	Simon Josefsson <simon@josefsson.org>,
	Bruno Haible <bruno@clisp.org>
Cc: Reuben Thomas <rrt@sc3d.org>, bug-gnulib <bug-gnulib@gnu.org>,
	Paul Smith <psmith@gnu.org>
Subject: Re: GNULIB_REVISION
Date: Thu, 25 Apr 2024 10:48:10 -0700	[thread overview]
Message-ID: <5bdc2190-72a3-4aee-baec-c9a229c4ec31@gmail.com> (raw)
In-Reply-To: <4a1d5684-f671-40df-9bd9-cb12dbd49c06@cs.ucla.edu>

On 4/25/24 10:00 AM, Paul Eggert wrote:
> Is there some way to cajole 'git clone' into using less memory, with a
> '--depth 1' or similar options? Cloning shallowly would clone Gnulib a
> lot faster, if you're cloning from a remote repository.

Maybe '--single-branch' would help too. If space is really desperate
the snapshots on gitweb are pretty small.

    https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commit;h=648aeb575db7af9ddd51cf17d1b56ee91e9ef3c5

7.6 MB for me vs. my full clone

$ du -s --human-readable .git
114M	.git

Collin


      parent reply	other threads:[~2024-04-25 17:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23 10:27 'relocatable' project built without --enable-relocatable Reuben Thomas
2024-04-23 19:46 ` Bruno Haible
2024-04-23 19:58   ` Reuben Thomas
2024-04-23 23:24     ` Bruno Haible
2024-04-24 20:36       ` Reuben Thomas
2024-04-25 12:07         ` Bruno Haible
2024-04-25 12:22           ` Reuben Thomas
2024-04-23 23:51     ` Gnulib in Debian Bruno Haible
2024-04-24 11:26       ` Reuben Thomas
2024-04-24 13:56         ` Simon Josefsson via Gnulib discussion list
2024-04-24 19:15           ` Reuben Thomas
2024-04-25 13:29           ` GNULIB_REVISION Bruno Haible
2024-04-25 16:26             ` GNULIB_REVISION Simon Josefsson via Gnulib discussion list
2024-04-25 17:00               ` GNULIB_REVISION Paul Eggert
2024-04-25 17:43                 ` GNULIB_REVISION Simon Josefsson via Gnulib discussion list
2024-04-25 18:49                   ` GNULIB_REVISION Paul Eggert
2024-04-25 17:48                 ` Collin Funk [this message]

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://lists.gnu.org/mailman/listinfo/bug-gnulib

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

  git send-email \
    --in-reply-to=5bdc2190-72a3-4aee-baec-c9a229c4ec31@gmail.com \
    --to=collin.funk1@gmail.com \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=psmith@gnu.org \
    --cc=rrt@sc3d.org \
    --cc=simon@josefsson.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. 
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).