1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Robin H. Johnson schrieb: |
5 |
> On Tue, Aug 26, 2008 at 04:57:50PM -0500, Yuri Vasilevski wrote: |
6 |
>> I am writing a tool that creates deb (as in Debian package format) based |
7 |
>> distributions from gentoo packages and that tool encodes the CVS |
8 |
>> revision as part of "debian revision" of the packages. So I need this |
9 |
>> part to be chronologically ordered, as opposed to have only the |
10 |
>> knowledge of whenever the file has changed or not. |
11 |
> <snip> |
12 |
> That is an interesting use case, and would that would present a problem |
13 |
> with any VCS migration. |
14 |
|
15 |
I don't see this problem ... I guess it is possible in all VCS to get |
16 |
the information, which global revision touched a specific file last. |
17 |
|
18 |
For example in bzr (these examples are conceived by me - so probably |
19 |
there is an easier way): |
20 |
|
21 |
bzr log -l1 --line $FILE | cut -f1 -d: |
22 |
|
23 |
- --or: to have the unique rev-id instead of the branch-local rev-number-- |
24 |
|
25 |
bzr log -l1 --show-ids $FILE | grep "revision-id" | cut -f2 -d' ' |
26 |
|
27 |
|
28 |
And hg,svn,git sure have similar abilities. |
29 |
|
30 |
- - Necoro |
31 |
-----BEGIN PGP SIGNATURE----- |
32 |
Version: GnuPG v2.0.9 (GNU/Linux) |
33 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
34 |
|
35 |
iEYEARECAAYFAki0hZQACgkQ4UOg/zhYFuBTrgCeJ/2gfygwUvWCB5QOibsYz0mN |
36 |
sGMAnRmqz/ChCg6zSAVrS4JljP1+DYRV |
37 |
=g5fE |
38 |
-----END PGP SIGNATURE----- |