From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] Re: git/fetch: be more robust
Date: Sun, 25 Jul 2021 21:39:09 -0400 [thread overview]
Message-ID: <E99384F6571323C6BB8D8CD8B5531D6F@eigenstate.org> (raw)
In-Reply-To: <YP4Dkxaoacmb7poU@alice>
Quoth Anthony Martin <ality@pbrane.org>:
> > memset(&have[nref], 0, sizeof(have[nref]));
> > - print("remote %s %H local %H\n", sp[1], want[nref], have[nref]);
> > nref++;
> > }
> > if(listonly){
>
> This will cause git/fetch -l to output nothing.
>
> Cheers,
> Anthony
>
Ah, you're right -- question, does anyone use '-l'?
Can I just kill it?
next prev parent reply other threads:[~2021-07-26 1:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 0:23 [9front] " ori
2021-07-26 0:36 ` [9front] " Anthony Martin
2021-07-26 1:39 ` ori [this message]
2021-07-26 0:45 ` [9front] " cinap_lenrek
2021-07-26 1:42 ` 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=E99384F6571323C6BB8D8CD8B5531D6F@eigenstate.org \
--to=ori@eigenstate.org \
--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).