continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Punkin Head <punkinsh...@gmail.com>
Subject Re: Error in detecting changes
Date Fri, 03 Feb 2006 14:49:01 GMT
The version in CVS is 1.34 (with an update by another individual) but, the
Continuum build number is 25.  On CVS 1.25 I was the one who commited the
changes and it is those comments that are on the Continuum build changes
page, not the ones from CVS version 1.34.

On 2/3/06, Emmanuel Venisse <emmanuel@venisse.net> wrote:
>
> What do you mean? What is a CVS revision?
>
> When continuum does a new build, it run the following command 'cvs -f -q
> update -d'
> A build number is internal to Continuum and cvs doesn't know it.
>
> Emmanuel
>
> Punkin Head a écrit :
> > When Continuum does a new build, it seems to detect the CVS revision
> that is
> > equivalent to the build number.  For example, one of our modules is on
> build
> > 25 but CVS revision 34 and the comments for the changes on the build
> result
> > page are from CVS revision 25.  Is there a way to match these so that we
> can
> > see who did what?
> >
> > Thanks,
> >
> > Adam
> >
> > --
> > www.punkinshred.net  // punkin'head official homepage
> >
> > www.myspace.com/punkinhead <-- for true shred
> >
>
>


--
www.punkinshred.net  // punkin'head official homepage

www.myspace.com/punkinhead <-- for true shred

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message