From: Norbert Preining <preining@logic.at>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: Creating something like increasing revision numbers
Date: Mon, 19 Oct 2009 02:44:47 +0200 [thread overview]
Message-ID: <20091019004447.GC11739@gamma.logic.tuwien.ac.at> (raw)
In-Reply-To: <alpine.LNX.2.00.0910181727130.32515@iabervon.org>
Hi all,
thanks everyone for the nice feedback!
On So, 18 Okt 2009, Daniel Barkalow wrote:
> It's possible as long as you don't think of the "version number" as a
> property of the commit, but rather a property that some commits get by
> virtue of having been at some time the commit that's what would be found
> on that particular server at that particular time. Even though the history
Right! That is a good point. In fact I don't care about (local) commits,
but about the pushes to the central server.
> of the *content* is non-linear, the sequence of values stored in
> refs/heads/master on your central server is linear, local, and easy to
> enumerate.
That is exactely what I need.
> Of course, when someone does a bunch of development in parallel with other
> people, does a final merge, and pushes it back to the server, this only
> increases the version by one, and only the final merge actually has a
As it is now with svn, we have to live with that. The point is that we
still would see many different commits pushed to the server, so
git log would show the single items, but the "versioning sequence number"
is only increased by one. That would be *absolutely*perfect* for me!
> because the intermediate commits don't ever get packages created of them
> to need to be compared to other packages.
Right!
Now my follow-up questions:
- how would one access this "sequence" number on the server
- is there a way to determine at which of this "sequence" numbers a specific
file has been changed last?
Thanks a lot and all the best
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
-------------------------------------------------------------------------------
DULEEK (n.)
Sudden realisation, as you lie in bed waiting for the alarm to go off,
that it should have gone off an hour ago.
--- Douglas Adams, The Meaning of Liff
next prev parent reply other threads:[~2009-10-19 0:44 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
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 [this message]
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=20091019004447.GC11739@gamma.logic.tuwien.ac.at \
--to=preining@logic.at \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).