From: qwx <qwx@sciops.net>
To: 9front@9front.org
Subject: Re: [9front] git: better handling of absolute paths, regex metachars
Date: Thu, 12 Aug 2021 16:27:47 +0200 [thread overview]
Message-ID: <F8529A0B2B9DD13ECD7A682BE4A31A6F@wopr.sciops.net> (raw)
In-Reply-To: <24F7706D609399B43057E1268EEBB3B8@eigenstate.org>
git/push has a typo: `sub' instead of `subst' in the change.
.git/fs may be removed from a remote git9 repo.
Example:
; git/commit .
heads/master: 72401e717205cf5864beebdcbacaefcd39ce8465
; git/push
deltifying 5 objects: 100%
writing 5 objects: 100%
sub: './sub' directory entry not found
sub: './sub' directory entry not found
usage: basename [-d] string [suffix]
/bin/git/push:41: > requires file
; rcpu -u qwx -h shithub.us
cpu% cd /usr/git/qwx/qk1
cpu% lc .git
HEAD config description info/ objects/ refs/ webpublish # shithub page now broken
Thanks,
qwx
next prev parent reply other threads:[~2021-08-13 1:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 19:43 ori
2021-08-12 14:27 ` qwx [this message]
2021-08-14 19:24 ` ori
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=F8529A0B2B9DD13ECD7A682BE4A31A6F@wopr.sciops.net \
--to=qwx@sciops.net \
--cc=9front@9front.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 NNTP newsgroup(s).