dumping ground for random patches and texts
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: spew@80x24.org
Subject: [PATCH] initial
Date: Sat,  8 Apr 2023 20:33:11 +0000	[thread overview]
Message-ID: <20230408203311.1370750-1-e@80x24.org> (raw)

---
 GNUmakefile | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 51 insertions(+)
 create mode 100644 GNUmakefile

diff --git a/GNUmakefile b/GNUmakefile
new file mode 100644
index 0000000..06a9416
--- /dev/null
+++ b/GNUmakefile
@@ -0,0 +1,51 @@
+all ::
+
+export GIT_TEST_FSYNC := 0
+#export PATH := /usr/lib/ccache:/usr/local/bin:/usr/bin:/bin
+
+include config.mak
+
+#torsocks eatmydata grok-pull -v -c repos.conf; test $$? -eq 127
+fetch-once:
+		chrt -i 0 ionice -c3 public-inbox-clone \
+		--inbox-config=never \
+		--exit-code \
+		--manifest= \
+		--objstore= \
+		--project-list= \
+		-p $(OPT) \
+		https://git.kernel.org/ .
+fetch :
+	err=0; while test $$err -eq 0; do \
+		chrt -i 0 ionice -c3 public-inbox-clone \
+		--inbox-config=never \
+		--exit-code \
+		--manifest= \
+		--objstore= \
+		--project-list= \
+		-p \
+		https://git.kernel.org/ .; \
+		err=$$?; echo err=$$err; \
+		if test $$err -eq 127; then exit $$err; fi; \
+	done
+
+fetch-loop :
+	while true; do \
+		echo pulling...; \
+		torsocks eatmydata grok-pull -v -c repos.conf; \
+		err=$$?; \
+		if test $$err -ne 127; then exit $$err; fi; \
+	done
+
+cindex :
+	@test -n "$(CIDX_DIR)" || \
+		{ echo >&2 'CIDX_DIR undefined in config.mak'; exit 1; }
+	chrt -i 0 ionice -c3 public-inbox-cindex \
+		-d $(CIDX_DIR) --no-fsync \
+		-L medium --max-size=10m $(OPT) -j3 \
+		--exclude='**/deps.git' \
+		--exclude='**/pgpkeys.git' \
+		--exclude='**/transparency-logs/**' \
+		--project-list=projects.list .
+
+.PHONY: fetch all fsck fetch-loop

                 reply	other threads:[~2023-04-08 20:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230408203311.1370750-1-e@80x24.org \
    --to=e@80x24.org \
    --cc=spew@80x24.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).