Benoit SIGOURE <[EMAIL PROTECTED]> writes:

>> -<pre><samp>git clone git://git.savannah.gnu.org/gnulib.git
>> +<pre><samp>git clone git://git.savannah.gnu.org/gnulib
>>  </samp></pre>
>>
>
> Is there any reason why this has changed?

It was to match what was in the README file for gnulib.

> I learned (the hard way) that for bare public repositories, it's
> better to stick to what turns out to be more than a naming
> convention of `project.git'.  I don't know if these issues are only
> related to dumb protocols (HTTP*) or if they also affect the Git
> protocol.  I can't find the relevant thread on the Git ML but the
> thing is that it seems that several tools rely on the fact that a
> repository name of the form `foo.git' implies that it's a bare
> repository (and thus it doesn't need to look for a nested .git
> directory).

I'm sorry, I wasn't aware of that issue.  I fixed both README
and gnulib.html.  Thanks.


Reply via email to