Re: [Codestriker-user] branch on some files only
Brought to you by:
sits
|
From: David S. <si...@us...> - 2004-10-24 23:41:03
|
Hi Dave, On Sun, 24 Oct 2004 02:53, Clendenan, Dave wrote: > In our development we have long-lived branches on some files for a few > projects, where the rest are taken from the tip. > > Using the branch tag in codestriker shows that all the files not on > the branch have been deleted, which makes for large, messy review > sets. Sending 'rdiff -f' solves this problem, so I was thinking I'd > add the option to select this behavior to the 'create new topic' page. This is an interesting option, I've never seen it before. Makes perfect sense in your case. I guess a new checkbox for this option with a (?) link explaining what it means would be good. I wonder if other SCM systems have a similar option. > I'm also planning on writing a simple script that'll add a tag to a > repository, and generate a codestriker topic comparing that tag with > the one from the previous run. This will be used for daily code > comparisons, in conjunction with a scheduled nightly build. > > If anyone has comments on how this should be done (or if it's already > done somewhere and I missed it :) please let me know. Make sure you use/extend the CodestrikerClient.pm module that lives in bin/. This is used by CVS commit scripts for automatically creating topics for each commit (see the commit_prep.pl and log_accum.pl files in the bin directory). This should give you a good head start. You'll need to modify CodestrikerClient.pm so that it can create topics usings tags. At the moment, it only creates topics from a file. It shouldn't be too hard to extend this. -- Cheers, David |