Re: CVS versioning
- From: "William" <Reply@xxxxxxxxxxxxxxxx>
- Date: Sun, 17 Apr 2005 13:13:54 -0500
<djake@xxxxxxxxx> wrote in message
news:1113575267.811468.269500@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
> OBSERVATION
> CVS assign to every source file a version.
>
> PROBLEM
> When i generate my executable and distribute it, i can't know the
> version of single source files.
We don't use CVS but I imagine something similar to this
will work using a label.
We generate a build number for each build that includes
the last change number (each change gets a unique number)
that went into the build. In general, that's all the
information I need to pick out exactly what source file
versions went into it. (Actually, knowing the date and
time of the build I can use that too.)
This fails if the build was made by skipping a few
changes prior to the change used to generate the build #.
In that case, I could create a label, giving it the
build # as a name, and use that. This might be more
like what you could do in CVS. -Wm
.
- Follow-Ups:
- Re: CVS versioning
- From: djake
- Re: CVS versioning
- References:
- CVS versioning
- From: djake
- CVS versioning
- Prev by Date: Re: programming job market in bay area in US
- Next by Date: Re: programming job market in bay area in US
- Previous by thread: Re: CVS versioning
- Next by thread: Re: CVS versioning
- Index(es):
Relevant Pages
|
