On Tue, Aug 21, 2018 at 12:04:20AM -0400, CrestChristopher wrote:
> > > > Okay, the way Git works via HTTP is actually documented in [1],
> > > > and trust me, you're supposed to read it several times to understand
> > > > completely.
> > > Documented in [1] ?
> > Exactly. The numbered reference
Sorry I don't follow ?
On 8/20/2018 9:08 AM, Konstantin Khomoutov wrote:
On Mon, Aug 20, 2018 at 07:24:12AM -0400, CrestChristopher wrote:
Okay, the way Git works via HTTP is actually documented in [1],
and trust me, you're supposed to read it several times to understand
completely.
On Mon, Aug 20, 2018 at 07:24:12AM -0400, CrestChristopher wrote:
>> Okay, the way Git works via HTTP is actually documented in [1],
>> and trust me, you're supposed to read it several times to understand
>> completely.
>
> Documented in [1] ?
Exactly. The numbered reference was at the mail's
Okay, the way Git works via HTTP is actually documented in [1],
and trust me, you're supposed to read it several times to understand
completely.
Documented in [1] ?
Crest
--
You received this message because you are subscribed to the Google Groups "Git for
human beings" group.
To
i fiddled around with it a few more hours and came to the conclusion that
this is hopeless. i decided to switch to gerrit codereview.
On Tuesday, August 14, 2018 at 7:32:28 PM UTC+2, Konstantin Khomoutov wrote:
>
> On Tue, Aug 14, 2018 at 02:24:30AM -0700, christia...@itsv.at
> wrote:
>
> > i
On Tue, Aug 14, 2018 at 02:24:30AM -0700, christian.tre...@itsv.at wrote:
> i am trying to set up gitweb and the http backend. gitweb works so far, but
> the http backend is giving me headaches. i always get "fatal: repository
> not found errors, which is quite frustrating as gitweb works
