From: "René 'Necoro' Neumann" <lists@necoro.eu>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Usages of CVS $Header$ keyword in ebuilds - use cases wanted
Date: Wed, 27 Aug 2008 01:19:17 +0200 [thread overview]
Message-ID: <48B48F75.6090707@necoro.eu> (raw)
In-Reply-To: <20080826225414.GJ30560@curie-int.orbis-terrarum.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Robin H. Johnson schrieb:
> On Wed, Aug 27, 2008 at 12:37:09AM +0200, Ren?? 'Necoro' Neumann wrote:
>> - --or: to have the unique rev-id instead of the branch-local rev-number--
>> bzr log -l1 --show-ids $FILE | grep "revision-id" | cut -f2 -d' '
> IIRC, the revision-id is just like the Git $Id$, it's a hex string, not
> an incremented counter like the revision number in CVS.
>
True ... it usually looks like
author@doma.in-20080821233630-v94w5lkebavkx9ti
Though, if one enforces certain policies using the "main branch" located
on the server like disallowing pushing and only allowing merges, one can
safely use the branch-revno (which is incremental). Only oddity are
revnos of merged branches (e.g. "193.1.10")
Another approach would be to use the unix-timestamp of the last change.
Though it is not a unique identifier per se, it should be sufficient here.
It should be queriable in all VCS. Though it might be, that it is not
possible using standard CLI and requires a plugin in some way (but I
bet, an easy one ;))
- - Necoro
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAki0j3UACgkQ4UOg/zhYFuDZ+QCdGm7Sjew2+27KCUB06lWf8aLr
XBsAoIbJSke4xHyPiucYEmkuNVd9GPJ3
=jTaO
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-08-26 23:19 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 20:40 [gentoo-dev] Usages of CVS $Header$ keyword in ebuilds - use cases wanted Robin H. Johnson
2008-08-26 20:41 ` Yuri Vasilevski
2008-08-26 20:54 ` Robin H. Johnson
2008-08-26 20:59 ` Yuri Vasilevski
2008-08-26 21:45 ` Robin H. Johnson
2008-08-26 21:57 ` Yuri Vasilevski
2008-08-26 22:25 ` Robin H. Johnson
2008-08-26 22:37 ` René 'Necoro' Neumann
2008-08-26 22:54 ` Robin H. Johnson
2008-08-26 23:19 ` René 'Necoro' Neumann [this message]
2008-08-26 23:28 ` René 'Necoro' Neumann
2008-08-26 22:46 ` Yuri Vasilevski
2008-08-26 22:46 ` Raúl Porcel
2008-08-27 16:35 ` Fabian Groffen
2008-08-27 17:28 ` Robin H. Johnson
2008-08-27 17:38 ` Fabian Groffen
2008-08-27 18:57 ` Alec Warner
2008-08-27 19:15 ` Robin H. Johnson
2008-08-27 19:24 ` Fabian Groffen
2008-08-27 19:16 ` Fabian Groffen
2008-08-26 20:46 ` Mart Raudsepp
2008-08-27 17:12 ` Paul Varner
2008-10-01 15:31 ` Thilo Bangert
2008-10-01 23:21 ` Robin H. Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48B48F75.6090707@necoro.eu \
--to=lists@necoro.eu \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox