tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Kristaps Dzonsons <kristaps@bsd.lv>
To: tech@mdocml.bsd.lv
Subject: Re: mdocml: Renamed mandoc.c to libmandoc.c.
Date: Tue, 06 Jul 2010 12:58:52 +0200	[thread overview]
Message-ID: <4C330C6C.2090202@bsd.lv> (raw)
In-Reply-To: <4C32F642.2090609@bsd.lv>

>> 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?
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

  reply	other threads:[~2010-07-06 11: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 [this message]
2010-07-06 22:01       ` Ingo Schwarze
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=4C330C6C.2090202@bsd.lv \
    --to=kristaps@bsd.lv \
    --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).