From: Ingo Schwarze <schwarze@usta.de>
To: tech@mdocml.bsd.lv
Subject: Re: mdocml: Renamed mandoc.c to libmandoc.c.
Date: Wed, 7 Jul 2010 00:01:00 +0200 [thread overview]
Message-ID: <20100706220100.GD19714@iris.usta.de> (raw)
In-Reply-To: <4C330C6C.2090202@bsd.lv>
Hi Kristaps,
>> I think this change ought to be undone. That is, undone on the
>> RCS level, not just reverted by renaming the file once more.
> I don't understand this. Isn't a `cvs add' good enough to resurrect the
> file after it's been removed?
Yes, it is, i only worried about the history, but even that it fully
preserved, as i just tested:
* create a file (rev. 1.1)
* change a line (rev. 1.2)
* delete the file (rev. 1.3)
* resurrect the file (rev. 1.4)
I assumed cvs annotate would then show 1.4 for all lines.
But it doesn't, it still shows 1.1 and 1.2 just like it did
before the removal; cvs annotate apparently just ignores the
deleted revision.
Thus, you are right, just cvs add & commit is the way to go.
Yours,
Ingo
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2010-07-06 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201007052000.o65K0uQH002309@krisdoz.my.domain>
2010-07-06 3:15 ` Ingo Schwarze
2010-07-06 9:24 ` Kristaps Dzonsons
2010-07-06 10:58 ` Kristaps Dzonsons
2010-07-06 22:01 ` Ingo Schwarze [this message]
2010-07-06 23:30 ` Ingo Schwarze
2010-07-07 10:56 ` Kristaps Dzonsons
2010-07-07 21:58 ` Ingo Schwarze
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=20100706220100.GD19714@iris.usta.de \
--to=schwarze@usta.de \
--cc=tech@mdocml.bsd.lv \
/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).