From: Norbert Preining <preining@logic.at>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johan Herland <johan@herland.net>, git@vger.kernel.org
Subject: Re: Creating something like increasing revision numbers
Date: Mon, 19 Oct 2009 02:48:29 +0200 [thread overview]
Message-ID: <20091019004829.GD11739@gamma.logic.tuwien.ac.at> (raw)
In-Reply-To: <7vfx9gnwtw.fsf@alter.siamese.dyndns.org>
On So, 18 Okt 2009, Junio C Hamano wrote:
> #2 Do not give such sequential number locally; the central repository is
> the _only_ place that assigns such a number. '?' stands for
> 'unnumbered'
[...]
> Scheme #2 is a way to get some stablility; give the authority of numbering
> to the central repository and commits that haven't hit the central
> repository are left unnumbered. But that is generally not very useful
> for your purpose of giving incrementing version number for building (the
> developers would want to build for testing before finally committing to
> publish the result to the central place).
That problem we have anyway with subversion, too, because as long as you
do not commit your changes nothing will happen on package rebuild.
So that is not a problem here.
Yes, we want server-sided linear numbers and anything *not* pushed to
the server is unnumbered.
And that is also fine, because packages are built only from the server.
Best wishes
Norbert
-------------------------------------------------------------------------------
Dr. Norbert Preining Associate Professor
JAIST Japan Advanced Institute of Science and Technology preining@jaist.ac.jp
Vienna University of Technology preining@logic.at
Debian Developer (Debian TeX Task Force) preining@debian.org
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
PUDSEY (n.)
The curious-shaped flat wads of dough left on a kitchen table after
someone has been cutting scones out of it.
--- Douglas Adams, The Meaning of Liff
next prev parent reply other threads:[~2009-10-19 0:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-18 14:41 Creating something like increasing revision numbers Norbert Preining
2009-10-18 15:03 ` Johan Herland
2009-10-18 15:20 ` Norbert Preining
2009-10-18 17:23 ` Johan Herland
2009-10-18 18:16 ` alexandrul
2009-10-19 1:15 ` Nicolas Pitre
2009-10-18 22:47 ` Junio C Hamano
2009-10-19 0:48 ` Norbert Preining [this message]
2009-10-18 15:29 ` alexandrul
2009-10-18 15:37 ` demerphq
2009-10-18 15:45 ` Norbert Preining
2009-10-18 16:16 ` demerphq
2009-10-18 16:35 ` alexandrul
2009-10-18 15:37 ` Jon Smirl
2009-10-18 21:43 ` Daniel Barkalow
2009-10-19 0:44 ` Norbert Preining
2009-10-19 1:16 ` Daniel Barkalow
2009-10-19 1:33 ` Norbert Preining
2009-10-19 2:41 ` Daniel Barkalow
2009-10-19 1:34 ` Nicolas Pitre
2009-10-19 1:42 ` Norbert Preining
2009-10-19 6:21 ` Johannes Sixt
2009-10-21 7:47 ` David Aguilar
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=20091019004829.GD11739@gamma.logic.tuwien.ac.at \
--to=preining@logic.at \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johan@herland.net \
/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;
as well as URLs for NNTP newsgroup(s).