[sslh] git repo?

[Jon Spriggs]

OK, somehow I completely failed to finish my train of thought (that'll
teach me to ... erm, do stuff, in erm ... something? :) )

Anyway, yehr, I tried running my own, but ultimately the ease of use
with Github won me over, and in the longer term got me several
drive-by commits on typos and documentation corrections.

Rgds,
--
Jon "The Nice Guy" Spriggs


On 10 July 2013 14:16, Jon Spriggs <jon at sprig.gs> wrote:
> Yves,
>
> In my opinion (and I might be in the minority here - my main use of
> Git has been with PHP, not a compiled language), I'd use a common
> central system with good issue and pull tracking facilities - such as
> Github or GitLab.
>
> I tried running my own Git repos for several of my projects, and
> ultimately, the stability and interface within Github, as well as the
> simplicity of cloning and tracking when online, plus permitting very
> simple drive-by commits (there's an inbuilt edit button now, which
> clones the repo and opens the file in your personal repo, and once
> you've done your edit then offers to submit a pull request - it's all
> an inline process, which is nice).
>
> Regards,
> --
> Jon "The Nice Guy" Spriggs
>
>
> On 10 July 2013 14:05, Yves Rutschle <yves at naryves.com> wrote:
>> On Tue, Jul 09, 2013 at 02:30:46PM -0400, Jason Cooper wrote:
>>> Darn, I was hoping to just untar, cleanup, commit, repeat ;-)
>>
>> Actually, that's probably what I'll do -- after checking it
>> out (so to speak), my SVN's history is of no value to
>> anyone, not even history.
>>
>>> I don't like imposing my way on other developers, particularly with
>>> their own projects.  But if you've been considering making the jump, I
>>> can say it would make patch submission a *lot* easier. <nudge, nudge>
>>>
>>> If that 'probably' turns out to be a 'yes', just yell.  I do quite a bit
>>> with git.  Yes, that rhymes, and no it wasn't intentional.  :)
>>
>> I only do a lil bit with git, but yesterday I wished I could
>> stash, so I'll fire up bash and enjoy git's hash (which is
>> sha). Ahem. :)
>>
>> More to the point, question to the experienced user: is a
>> public HTTP repository OK, or is it much better to have a
>> git daemon? I strongly tend towards HTTP to avoid a new
>> service (and then I'd need to add git support to sslh...)
>> but I'm not sure that's not overly restrictive.
>>
>> Cheers,
>> Y.
>>
>>
>> _______________________________________________
>> sslh mailing list
>> sslh at rutschle.net
>> http://rutschle.net/cgi-bin/mailman/listinfo/sslh