From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: tuhs@tuhs.org
Subject: Re: [TUHS] qed-archive - please reclone
Date: Wed, 30 Jan 2019 20:16:34 +0100 [thread overview]
Message-ID: <20190130191634.ExRH-%steffen@sdaoden.eu> (raw)
In-Reply-To: <201901301622.x0UGMpP0028555@freefriends.org>
arnold@skeeve.com wrote in <201901301622.x0UGMpP0028555@freefriends.org>:
|Hi All.
|
|I had a bad commit message in the qed-archive I mentioned here a few weeks
|ago. I fixed it with a 'git push --force' (even though that's not
|recommended) since I expect it to be a read-only archive going forward,
|and I wanted it to be right.
|
|In short, if you cloned it, please remove your copy and reclone.
Just "fetch -f" over your "push -f" commits, no need to reclone.
--End of <201901301622.x0UGMpP0028555@freefriends.org>
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
prev parent reply other threads:[~2019-01-30 19:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 16:22 arnold
2019-01-30 19:14 ` Donald ODona
2019-01-30 19:16 ` Steffen Nurpmeso [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190130191634.ExRH-%steffen@sdaoden.eu \
--to=steffen@sdaoden.eu \
--cc=tuhs@tuhs.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).