pipfsta...@openmailbox.org wrote:
> Hello,
> 
> CVS is delivering me my daily dose of PITA (and I'm delivering a daily
> dose of whining to the list). I feel like I'm trying to use a wooden bicycle
> driven by jolts from the ground to make a tour from Washington, DC to
> Sacramento, California.
> 
> I've found cvs2cl.pl that turns pretty useless output of `cvs log` into
> something meaningful.
> But I didn't made my way through branches and tags.
> I know that when release is done, sources are tagged with a
> 'OPENBSD_x_y_BASE' tag. But cvs doesn't provide a way (well, at least
> I didn't find it) to find a commit id when a certain tag was created.
> Well, I tried to grep (1) the raw output of cvs log to see how tags
> refer to files in per-file basis. But some files don't have any symbolic
> names at all!
> E.g.:
> 
> "RCS file: /cvs/src/sys/arch/armv7/sunxi/Attic/sximmc.c,v
> Working file: sys/arch/armv7/sunxi/sximmc.c
> head: 1.12
> branch:
> locks: strict
> access list:
> symbolic names:
> keyword substitution: kv
> total revisions: 12;
> selected revisions: 12"
> 
> And it is not a new file, first revision is dated 2016/08/15. It might
> be some development branch, but then how do I differ which commits are
> made into a release, and which are not?

well, you're looking at a file that was deleted before it made it into any
releases. it's not going to have tags.

> Is there any way to make cvs show a bunch of changes that are made
> between two releases in the -CURRENT and -STABLE branches?

cvs diff -rOPENBSD_6_1 -rHEAD ?

it's not clear what you're really trying to do. if you want the files for a
release, cvs co -r that release.

Reply via email to