GitHub has been such a staple of the modern dev that some are now (re)discovering git is distributed.
Everything old is new again. I wouldn't be surprised if there were people that thought GitHub invented git.
Local Git remotes
41–50 of 85 posts
Re: Local Git remotes
#42I love reading articles like this. It's kinda of a slap in the face – "hey guys, you know that thing you've been doing for decades, well for decades you've had this ability to do it with your own stuff if you just spend a few human brain tokens on it". btw, Git also supports the HTTP protocol ...
Re: Local Git remotes
#43GitHub has been such a staple of the modern dev that some are now (re)discovering git is distributed.
Everything old is new again. I wouldn't be surprised if there were people that thought GitHub invented git.
Re: Local Git remotes
#44What's the purpose of this? I don't get it. Why push at all to "local remote", if you can just keep your changes on a local branch, and push it whenever "remote remote" becomes available again?
I am also seriously puzzled and don't see the point. Why push to a local remote if the real remote is not reachable? The branch is still not leaving your machine, you are just making a copy of it in another place and now have to manage `local/` refs in addition to `origin/`.
Re: Local Git remotes
#45Earlier quoted context omitted.
I am also seriously puzzled and don't see the point. Why push to a local remote if the real remote is not reachable? The branch is still not leaving your machine, you are just making a copy of it in another place and now have to manage `local/` refs in addition to `origin/`.
It's useful for me to have a "production" website remote that i just run on my computer for myself locally. rsync could also work but tagging with rollbacks make it easier if something goes wrong. it's not a common thing but it's nice to have that as an option. just because you can't see the utility of it doesn't make it useless
Re: Local Git remotes
#46Re: Local Git remotes
#47Earlier quoted context omitted.
> thought GitHub invented git Putting the generic term into your corporation's name can be effective means of claiming things that don't belong to you. Jon Postel reserved 44.0.0.0/8 for a generic purpose: "amateur radio digital communications." Decades later, there was a successful heist when some enterprising individuals who had incorporated "Amateur Radio Digital Communications" misrepresented to ARIN that the ass…
Do you have a source for your claims about the ARDC?
The head of ARIN defends[1] the transfer throughout the thread.
[0]: https://seclists.org/nanog/2019/Jul/366 [1]: https://seclists.org/nanog/2019/Jul/458
Re: Local Git remotes
#48What's the purpose of this? I don't get it. Why push at all to "local remote", if you can just keep your changes on a local branch, and push it whenever "remote remote" becomes available again?
I use local remotes all the time for testing as a form of "local CI". Check it out from '/tmp' and make sure it still builds. For a single-dev or small team, it beats having to do github runner epicycles to accomplish the same basic goal. Add in Firejail if you want environment isolation.
Re: Local Git remotes
#49What's the purpose of this? I don't get it. Why push at all to "local remote", if you can just keep your changes on a local branch, and push it whenever "remote remote" becomes available again?
Re: Local Git remotes
#50What's the purpose of this? I don't get it. Why push at all to "local remote", if you can just keep your changes on a local branch, and push it whenever "remote remote" becomes available again?