Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fork direction is misleading #9

Closed
nponeccop opened this issue Sep 10, 2017 · 4 comments
Closed

Fork direction is misleading #9

nponeccop opened this issue Sep 10, 2017 · 4 comments

Comments

@nponeccop
Copy link

I don't know how to fix it. Maybe deleting this repo and forking from gearman/gearmand will do.

@p-alik
Copy link
Owner

p-alik commented Sep 10, 2017

This repo is ahead of [gearman/gearmand]. See #134

@nponeccop
Copy link
Author

It's still not a common practice. The "main" repo is gearman/gearmand, so a common approach is to use branches there if you want separate development branch.

It's up to you though. IMO you should at least document this uncommon structure of repos and using forks instead of branches in Readme.md of gearman/gearmand.

@p-alik
Copy link
Owner

p-alik commented Sep 11, 2017

I'm deeply disappointed to mislead you, but I had a particular reason to take ahead of origin repo.

IMO you should at least document this uncommon structure of repos and using forks instead of branches in Readme.md of gearman/gearmand.

It's mentioned in repo description: This repository may be slightly ahead of the https://github.com/gearman/gearmand

@nponeccop
Copy link
Author

Being ahead or behind is unrelated to forking direction. I don't understand why you put being ahead as an argument. Anyway, it's a minor issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants