On 29Mar2019 13:05, felixs <[email protected]> wrote:
On Fri, Mar 29, 2019 at 08:42:33AM +1100, Cameron Simpson wrote:
On 28Mar2019 22:20, felixs <[email protected]> wrote:
> I tried to access the branch with the patch, but the access is
> password-protected. Are you able to share the patchfile by other means?
> Signing up with gitlab is another option, but I'd need some more time to
> decide on whether it's the right choice for me.
You can sign up to github without any other obligations; it is free and gets
you various useful facilities.
For example, my own code is published on bitbucket, but I have a github
account in order to interoperate with various projects.
There isn't actually any particular downside.
Thanks for your comment, but already using gcloud I keep thinking about
the comparative benefits of using another 'big player' like gitlab, github
or platforms alike. I checked my possibilities/resources of code developing and
cannot see the 'upsides' (sorry for the neologism) of using another
service. But please tell me.
Mainly for interoperation with others. As I mentioned, I host my own
code on bitbucket, but have github and gitlab accounts so that I can
interact with projects hosted there.
For your own code, you can do as you want. When you want to submit to
other projects it is a great help to have an account with their repo
hosting service.
Elaboration:
You can generally git/hg clone from such services without an account
(i.e. public code repos like mutt) but if you want to make pull requests
the workflow is:
- fork the repo to your own account on that service
- clone your fork to your local environment
- make new stuff in a branch, and push that back to your fork
- push the "submit PR" button on the fork's web page, which presents
your fork's branch as a nice pull request to the original project
PR requests are generally implemented on a reference to the branch in
your fork on the service, so (a) the PR sees updates if you update your
fork's branch and (b) because the fork and PR were made via the service
(eg github/gitlab) all the references are tracked automatically: forking
knows where the fork came from and PR requests thus know how to submit
things back.
Therefore if your want to submit code _to_ a project it helps a great
deal to have an account with the hosting web service.
If, as you do, you just need access to the repo you don't normally need
an account; the usual VCS clone operations will do just fine, or you can
download the diff directly through the web interface.
OK, Google strives for getting more user data, but we know
that and can act accordingly.
Yeah. I try to use Google services sparingly. I have a GMail account,
but it forwards. I usually search with duckduckgo. And so on.
It's more: to get a good overwiew of innovative
technologies (and diving into it) I cannot see any other platform that has such
a broad approach.
The broad approach brings lock in. I try to think in terms of specific
services. Like supermarket loyalty cards, use of a single platform for
everything warps my decisions, so I try not to do that.
Anyway, I'm not trying to drive you to joins every service on the
planet, or recommending github/gitlab/etc in particular. I'm just saying
having an account costs no $s and will aid certain activities. Do it as
needed. Or not, if you'd rather not.
Cheers,
Cameron Simpson <[email protected]>
