Subject: Dumb HTTP & Caching
Date: Sat, 11 Apr 2020 23:59:02 +0200 [thread overview]
Message-ID: <5ab1e63c-b58e-b2c0-f650-224028201577@necoro.eu> (raw)
Hi,
I'm using cgit as a dumb HTTP frontend to my git repositories. And I
noticed that sometimes git push (via ssh) followed by git pull (via
https) will return the revision before the push.
Is it possible, that cgit's caching interferes with pull here? If so, is
there some way to turn it off without disabling caching as a whole?
Thanks and best regards,
Ren?
next reply other threads:[~2020-04-11 21:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 21:59 [this message]
2020-04-11 22:08 ` june
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=5ab1e63c-b58e-b2c0-f650-224028201577@necoro.eu \
--to=cgit@lists.zx2c4.com \
--subject='Re: Dumb HTTP & Caching' \
/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
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).