Sorry about that - a recent PR that was merged changed the routes that
handled this for some reason.  I just added the historical routes back
and they all should work again.

Scott

On Wed, May 1, 2013 at 8:57 PM, Konstantin Khomoutov
<kostix+...@007spb.ru> wrote:
> On Wed, 1 May 2013 14:38:02 -0400
> Jeff King <p...@peff.net> wrote:
>
> [...]
>> > Recently I discovered that a number of useful articles which sort of
>> > accompanied the "Pro Git" book are now inaccessible (404), namely:
>> > "Smart HTTP Transport" [1], "Reset Demystified" [2], "Note to
>> > Self" [3] and "Git Loves the Environment" [4].  I wonder if this is
>> > a known problem and/or whom I could contact about this issue?
>> >
>> > 1. http://git-scm.com/2010/03/04/smart-http.html
>> > 2. http://git-scm.com/2011/07/11/reset.html
>> > 3. http://git-scm.com/2010/08/25/notes.html
>> > 4. http://git-scm.com/2010/04/11/environment.html
>>
>> I think those links were broken by the site reorganization about a
>> year ago. You can get to them at:
>>
>>   http://git-scm.com/blog/2010/03/04/smart-http.html
>
> Oh, I was about to respond that links I referred to are returned by
> Google search for their respective article titles (it did so
> yesterday).  So I went to verify this and just observed that Google
> started to return liks pointing to (supposedly) Scott Chacon's site,
> like
>
>   http://scottchacon.com/2011/07/11/reset.html
>
> for the "Reset demystified" article.  Hence I suppose Scott was
> just transferring those articles to their new home.
>
>> and so on. In general, problems with git-scm.com should be reported
>> at:
>>
>>   https://github.com/github/gitscm-next
>
> Thanks!
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to