It happens sometimes that you need to split (aka "fork") a project of from 
the original source base.
This split (aka "fork") is supposed to then become a distinct project on 
it's own, and should never again rub shoulders with the original parent 
project.

Personally, I *despise*  this situation, since it boils down to 
"copy-paste-modify" projects. It is usually a direct result of a surprise 
(and URGENT) request/need from sales people to have a "skinned" version of 
an existing product/system to demo to potential clients.
The problem is that these abominations quite frequently then get sold - you 
know...*skinned*. But that "skinning" usually means EXTENSIVE changes and 
customizations - so much so that letting any of that code touch the 
original source would probably result in the universe imploding. 

SO if there was a way to make a branch that could never-every be merged 
into master (for example) that would sorta help. But would not completely 
solve it.

The only work-a-round I can think of atm is to push a branch to newly 
created project....which could work, and would be technically what I need, 
but feels very kludgy.

On Saturday, 1 June 2013 02:00:49 UTC+2, Aaron Cook wrote:
>
> What is the benefit of forking as opposed to branching in a small gitlab 
> server case?
>
> On Friday, May 31, 2013 8:40:50 AM UTC-4, Peter Cole wrote:
>
>> I was extremely excited for v5.2 to drop so I would finally be able to 
>> fork, which I assumed would be like GitHub or BitBucket. Instead, you 
>> apparently fork with no ties to the original project and cannot create 
>> merge requests between the two projects. Am I missing something? How is 
>> this useful?
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"GitLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to gitlabhq+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/gitlabhq/a7f22326-6e10-4757-9a90-35a625a709a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to