git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: demerphq <demerphq@gmail.com>
To: alexandrul <alexandrul.ct@gmail.com>
Cc: Norbert Preining <preining@logic.at>, git@vger.kernel.org
Subject: Re: Creating something like increasing revision numbers
Date: Sun, 18 Oct 2009 17:37:38 +0200	[thread overview]
Message-ID: <9b18b3110910180837h18e15f74g74626847b6ce4da3@mail.gmail.com> (raw)
In-Reply-To: <4ADB3452.6030508@gmail.com>

2009/10/18 alexandrul <alexandrul.ct@gmail.com>:
> Norbert Preining wrote:
>> My idea is that git - like subversion - could (if asked to) count each
>> commit (global to the repository, irrelevant of the branch) and give it
>> a version number. Since we all will use a bare repository on a server
>> and pull/push from/to there, I think that something similar could be possible.
>
> I was thinking to set a post-commit hook that reads the current version
> from a file, increment and save it, and also set a tag with that value.
>
> Being a DVCS, this kind of versioning can only be trusted on a single repo,
> but if you set it on the "main" repo, it should work.
>
> The only drawback could be the ever growing number of tags,
> I don't know how it will work with thousands of tags or more.

I think the other drawback is that the number would essentially be
meaningless and more or less would just be a substitute sha1.

Consider when a remote adds commits and then merges and pushes. What
number should those commits have?

Yves



-- 
perl -Mre=debug -e "/just|another|perl|hacker/"

  reply	other threads:[~2009-10-18 15:37 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 [this message]
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=9b18b3110910180837h18e15f74g74626847b6ce4da3@mail.gmail.com \
    --to=demerphq@gmail.com \
    --cc=alexandrul.ct@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=preining@logic.at \
    /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).