1 |
On Tue, 26 Aug 2008 14:45:25 -0700 |
2 |
"Robin H. Johnson" <robbat2@g.o> wrote: |
3 |
|
4 |
> On Tue, Aug 26, 2008 at 03:59:09PM -0500, Yuri Vasilevski wrote: |
5 |
> > > Err, what do you mean by revision dump? |
6 |
> > revision dump is when foo-1.0-r4 becomes foo-1.0-r5. |
7 |
> That's revision 'B'ump, not 'D'ump. |
8 |
|
9 |
Sorry, not native English speaker :$ |
10 |
|
11 |
> > But when foo-1.0-r4 is updated in-place, I use CVS revisions |
12 |
> > (ej: 1.12 -> 1.13 in 2nd word in $ Header: ....) |
13 |
> The $Header$ is filled out automatically by CVS, what are you using |
14 |
> the $Header$ string for? |
15 |
> |
16 |
> Why do you need to identify the changes? Considering that the checksum |
17 |
> changes as well, is detecting change not sufficient? (or asking the |
18 |
> VCS for what files have changed since your last check time). |
19 |
|
20 |
I am writing a tool that creates deb (as in Debian package format) based |
21 |
distributions from gentoo packages and that tool encodes the CVS |
22 |
revision as part of "debian revision" of the packages. So I need this |
23 |
part to be chronologically ordered, as opposed to have only the |
24 |
knowledge of whenever the file has changed or not. |