Re: minimize_url in git-svn?

From: Junio C Hamano <junkio@cox.net>
Date: May 9, 2007, 04:56 UTC
Message-ID: <7vhcqmzjaj.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <20070508193455.GA14602@muzzle>

Eric Wong <normalperson@yhbt.net> writes:

> .rev_db is offset-based database.  Revision numbers to git commits can
> be looked up using (SVN revision * 41).

Ah, that explains why the file looks so sparse. Their trunk/ seems to be somewhat inactive and activities elsewhere in the branch/ namespace we cannot view may advance SVN revisions.

Show 10 quoted lines

>>  * Assuming there aren't any damage, or maybe some damage that
>>    would cause minor decreased functionality/interoperability,
>>    would it perhaps make sense to optionally allow skipping the
>>    minimizing to avoid this problem?  Would it make sense, or is
>>    the setting at socialtext site too esoteric and it isn't
>>    worth to worry about?
>
> It *should* be automatically detecting the highest level up it can
> access and stop there.  In your case, there's obviously something
> broken in my code :(

Perhaps, but if the user has the proper user identity to access the full site, I suspect you would be better off getting the credential and connect to the higher level. In other words, the definition of "the highest level up it can access" depends on the user and what the user is trying to do (i.e. a user who does have an account with that project may not be interested in getting tags/ nor branches/, in which case the user may want to be able to say "I am not interested in uplevel" upfront, so that the program does not even have to ask for the password. On the other hand the user may want to access tags/ and branches/ in which case the user would appreciate the current behaviour, asking for the password and go up after authenticated).

Show 10 quoted lines

> I've definitely tested this as working against Seth Falcon's hedgehog
> repo (URL is somewhere in the archives).  I also setup a test repository
> somewhere that I can double-check against.
>
>> [Footnote]
>> 
>> *1* http://www.socialtext.net/stoss/index.cgi?developing_with_a_dev_env
>
> I'll try to take a look at that in the next few days.  I also have
> segfaults to fix that I haven't gotten to :(

Thanks. If I type <Return> instead of ^C in the transcript at the beginning of my message, I get a segfault. It may or may not be the same one you have been chasing.