From: "Sebastian Spaeth" <Sebastian@SSpaeth.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Make some big but only formal change before next stable - SRCPV
Date: Wed, 10 Mar 2010 10:48:03 +0100 [thread overview]
Message-ID: <87tysozewc.fsf@SSpaeth.de> (raw)
In-Reply-To: <1268167320.5437.2037.camel@lenovo.internal.reciva.com>
On Tue, 09 Mar 2010 20:41:59 +0000, Phil Blundell <philb@gnu.org> wrote:
> That does rather sound like a further argument for just not using the
> local count variables at all and just figuring out a monotonic count
> from the SCM (using git-rev-list or whatever) at packaging time.
That sounds rather nice, however I am not sure if git easily gives you
such a number. I know that mercurial does.
spaetz
next prev parent reply other threads:[~2010-03-10 9:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 7:53 [RFC] Make some big but only formal change before next stable - SRCPV Martin Jansa
2010-03-09 10:36 ` Phil Blundell
2010-03-09 11:59 ` Martin Jansa
2010-03-09 16:33 ` Phil Blundell
2010-03-09 14:00 ` Koen Kooi
2010-03-09 20:41 ` Phil Blundell
2010-03-10 9:48 ` Sebastian Spaeth [this message]
2010-03-10 14:56 ` Koen Kooi
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=87tysozewc.fsf@SSpaeth.de \
--to=sebastian@sspaeth.de \
--cc=openembedded-devel@lists.openembedded.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