Canonical fork? about git-sh HOT 5 OPEN

On Nov 24, 2018, at 4:26 PM, roeme ***@***.***> wrote: Heyo @krlmlr; to answer your inquiry related to my own fork; while I did fork rtomayko's original repo; in my case I did a more-or-less-greenfield approach later on in https://github.com/roeme/shgit. It does reuse some conceptual parts of git-sh, but is scoped to be (much) more light-weight (as my $DAYJOB requires working under cygwin, which incurs heavy penalties to some syscalls), have less dependencies (no make install), obey/hook into git configuration conventions as much as possible, to be as minimally intrusive as possible (load user rc files etc.), among others. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

On Sun, Nov 25, 2018 at 6:44 PM sr ***@***.***> wrote: i missed the fork and will be trying i made some personal hacks i merged on each pull that conflicted Sam Rash ***@***.*** > On Nov 24, 2018, at 4:26 PM, roeme ***@***.***> wrote: > > Heyo @krlmlr; to answer your inquiry related to my own fork; while I did fork rtomayko's original repo; in my case I did a more-or-less-greenfield approach later on in https://github.com/roeme/shgit. It does reuse some conceptual parts of git-sh, but is scoped to be (much) more light-weight (as my $DAYJOB requires working under cygwin, which incurs heavy penalties to some syscalls), have less dependencies (no make install), obey/hook into git configuration conventions as much as possible, to be as minimally intrusive as possible (load user rc files etc.), among others. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub, or mute the thread. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABEKE2PewoJmQbI48HhM9vX8RwI9h_rkks5uyytDgaJpZM4Yxlmu> .