From: Russ Allbery <rra@stanford.edu>
Subject: Re: CVS stuff in order; apply patches at will
Date: Mon, 05 Jan 2004 11:47:41 -0800 [thread overview]
Message-ID: <87n092yy76.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <m3d69z2wp0.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sun, 04 Jan 2004 23:08:59 +0100")
Lars Magne Ingebrigtsen <larsi@quimbies.gnus.org> writes:
> (And for some reason or other, "cvs commit -r7.1" made the cvs server
> send out patches between /dev/null and the entire repository.
> That's... not very useful.)
The CVS logging hooks don't seem to work properly with explicit revisions
specified with -r. I haven't managed to find a good way of fixing them,
but I also haven't investigated at length. They seem to report file
information to the logging scripts that's indistinguishable from a new
file add.
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~2004-01-05 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-04 22:08 Lars Magne Ingebrigtsen
2004-01-05 19:47 ` Russ Allbery [this message]
2004-01-06 5:01 ` Lars Magne Ingebrigtsen
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=87n092yy76.fsf@windlord.stanford.edu \
--to=rra@stanford.edu \
/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).