On 21 September 2015 at 02:30, David Narvaez wrote:
> On Sun, Sep 20, 2015 at 7:57 PM, Jaroslaw Staniek wrote:
>> I see you're not used to the diverse term on github-alike sites:
>> forking is more like creating a feature branch. The repo is separate
On 21 September 2015 at 01:27, Michael Pyne wrote:
> On Mon, September 21, 2015 00:05:33 Jaroslaw Staniek wrote:
>> PS: Freedom of forking - derivative works is not so terrible, it's a
>> pilliar of FOSS.
>
> Last time I tried it, running git-clone against our KDE git
On Sun, Sep 20, 2015 at 6:05 PM, Jaroslaw Staniek wrote:
> This is about r-w git repo for KDE and non-KDE devs.
> In git times the need is easier to understand for someone who
> interacts with 3rd party projects at code level.
>
> What is your workflow in this case?
> Do you send
On Mon, September 21, 2015 00:05:33 Jaroslaw Staniek wrote:
> PS: Freedom of forking - derivative works is not so terrible, it's a
> pilliar of FOSS.
Last time I tried it, running git-clone against our KDE git infrastructure
still worked just fine, and thus forking is quite easy to do. Did this
On Sun, Sep 20, 2015 at 7:57 PM, Jaroslaw Staniek wrote:
> I see you're not used to the diverse term on github-alike sites:
> forking is more like creating a feature branch. The repo is separate
> but changes can be merged back (how it's a matter of tool set).
It is just like
On 20 September 2015 at 23:55, David Narvaez wrote:
> On Sun, Sep 20, 2015 at 4:11 PM, Jaroslaw Staniek wrote:
>> Hi
>> I'd like to ask if this can be technically feasible and something we want:
>
>
>
> The subject sounds to me like a terrible idea,