From: "Per Abrahamsen" <per.abrahamsen@gmail.com>
To: "Reiner Steib" <Reiner.Steib@gmx.de>,
"Per Abrahamsen" <per.abrahamsen@gmail.com>,
"Bastien Guerry" <bzg@altern.org>,
ding@gnus.org
Subject: Re: cvs repository corruption
Date: Sun, 16 Mar 2008 19:25:19 +0100 [thread overview]
Message-ID: <66a8b7a0803161125k5e5358c2sa7236bbc0b11865b@mail.gmail.com> (raw)
In-Reply-To: <v9myoyimxu.fsf@marauder.physik.uni-ulm.de>
I found this message searching for the Bastien's report:
http://article.gmane.org/gmane.emacs.gnus.general/60810
Not sure if the patch was applied or not.
I don't know much about cvs. Would it work simply to remove the file
from the repository, and add a fresh copy?
History would be lost, but at least the file would be syntactically valid.
next prev parent reply other threads:[~2008-03-16 18:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-15 13:44 Per Abrahamsen
2008-03-16 17:43 ` Reiner Steib
2008-03-16 18:25 ` Per Abrahamsen [this message]
2008-03-16 19:37 ` Reiner Steib
2008-03-17 20:20 ` Andreas Schwab
2008-03-17 21:29 ` Reiner Steib
2008-03-17 21:42 ` Andreas Schwab
2008-03-19 13:53 ` cvs repository corruption (gnus-uu.el,v) Reiner Steib
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=66a8b7a0803161125k5e5358c2sa7236bbc0b11865b@mail.gmail.com \
--to=per.abrahamsen@gmail.com \
--cc=Reiner.Steib@gmx.de \
--cc=bzg@altern.org \
--cc=ding@gnus.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).