git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "André Goddard Rosa" <andre.goddard@gmail.com>
To: "Stephen Haberman" <stephen@exigencecorp.com>
Cc: "Thomas Rast" <trast@student.ethz.ch>,
	"Jakub Narebski" <jnareb@gmail.com>,
	marceloribeiro <marcelo@sonnay.com>,
	git@vger.kernel.org
Subject: Re: Numeric Revision Names?
Date: Sun, 5 Oct 2008 00:13:43 -0300	[thread overview]
Message-ID: <b8bf37780810042013g57fc7073xd638e44bb666bf@mail.gmail.com> (raw)
In-Reply-To: <20081003124224.843a5a21.stephen@exigencecorp.com>

> For projects that do have a central authority (e.g. internal corporate
> projects), revision numbers make more sense.

Surely!

> Granted, they are on separate branches (like svn), but the nice thing
> about them is that they are monotonically increasing. E.g. our qa
> people love numbers--the bug fix ticket says dev just put in
> r100...qa/production box says it is on r95. Doesn't matter the
> branch/whatever, they know the box doesn't have r100. Now, right, if
> its r105, it is trickier, although we also throw in branch name (e.g.
> topica-r100) which means no false positives but can lead to false
> negatives.

Yes

> haven't gotten to it yet. For now I've just attached the commit
> numbers script.

It would be good to have this feature in git.

> For our team, lack of monotonic version numbers was a big deal--as in
> can't use git sort of big deal. I wouldn't be surprised if it is a

Yes, it's true that this is a big deal for many people out there.

> contributing factor that keeps other people, especially internal teams,
> from git. I understand all of the reasons it can't be in git proper,
> but an FAQ entry about the hook/tag hack or link to a contrib script
> might be useful (not necessarily the one attached, given its
> functions/etc. baggage).

That would be helpful, if it cannot go in git proper for real in the
centralized model.

> (I also face/faced a situation where "monotonic revision numbers" were
> essentially a check box item on a required list of SCM features, so
> despite whatever I/the-git-team/etc. thought about their technical
> inferiority, it was a criteria that could have ruled git out for us.
> Hence my mentioning an FAQ entry for others faced with my same
> political situation.)
>

This is so true in a corporate environment with centralized
repositories, then I completely agree
that in the case git is being used in this model (many companies are
really used to that), the
monotonic revision number is helpful and sometimes is showstopper to
not have them.

Regards,
-- 
[]s,
André Goddard

  reply	other threads:[~2008-10-05  3:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-03 12:37 Numeric Revision Names? marceloribeiro
2008-10-03 12:41 ` Robin Burchell
2008-10-03 12:44 ` Bruce Stephens
2008-10-03 16:07 ` Jakub Narebski
2008-10-03 16:55   ` Stephen Haberman
2008-10-03 17:13     ` Thomas Rast
2008-10-03 17:42       ` Stephen Haberman
2008-10-05  3:13         ` André Goddard Rosa [this message]
2008-10-05  9:19           ` Alex Riesen
2008-10-03 17:14     ` Jeff King
2008-10-03 17:37       ` Jeff King

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=b8bf37780810042013g57fc7073xd638e44bb666bf@mail.gmail.com \
    --to=andre.goddard@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=marcelo@sonnay.com \
    --cc=stephen@exigencecorp.com \
    --cc=trast@student.ethz.ch \
    /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).