Re: Subversion-style incrementing revision numbers

From: Shawn Pearce <spearce@spearce.org>
Date: Sep 19, 2006, 22:23 UTC
Message-ID: <20060919222352.GC11601@spearce.org>
In-Reply-To: <eeppkl$rm9$2@sea.gmane.org>

Jakub Narebski <jnareb@gmail.com> wrote:

Show 15 quoted lines

> Joel Dice wrote:
> > Proposal:
> > 
> > As with Subversion, the IRN state in Git would be specific to a given 
> > repository and have no significance beyond that repository.  Also like 
> > Subversion, IRN state would be global across a repository, so that a 
> > commit to any branch would increment the current IRN value.  Every Git 
> > command taking a revision parameter would accept an IRN using a syntax 
> > such as "r$IRN".  Every commit would report the IRN to the user as well as 
> > the SHA ID.  The IRN feature could be enabled or disabled via a 
> > configuration option.
> 
> This of course limits IRN much. Tags are valid across repositories.
> I'm not sure if many repositories are managed using shared repositories
> (centralized approach).

Not only that but its somewhat difficult to execute `git log v1.4.0..v1.4.1` on a central repository; if IRNs are only valid within that repository then that's the only way they could even be used.

Note that somewhat difficult here means you need to:

	- gain direct read-only access to the repository's files (not
	  all systems may be able to offer this to all users);

	- set GIT_DIR environment variable OR pass --git-dir before
	  the subcommand;

	- do all of that without doing something stupid in the
	  repository directory such as `rm *` without realizing
	  where you are;

	- but still maintain write access so you can push.

and that latter GIT_DIR/--git-dir part users are bound to forgot as its not as natural as just assuming the repository is the directory you are in. Of course that could be probably fixed...

-- 
Shawn.