git as the primary backend for revision history and patches, but hmmm 🤔
git as the primary backend for revision history and patches, but hmmm 🤔
git as the primary backend for revision history and patches, but hmmm 🤔
git as the primary backend for revision history and patches, but hmmm 🤔
git itself basically just houses some client-side "Metadata" about the repository and a bunch of objects that make up the contents and revision history. For example, there is a special file called .git/description that you can edit and there's even git branch --edit to edit a branch's description. But none of that is useful beyond a local client. That is to say, if you git clone or git push none of that information is published anywhere or made available to anyone else.So Git's "distributed data" is limited to well basically its revision history and series of objects I guess? 🤔
git itself basically just houses some client-side "Metadata" about the repository and a bunch of objects that make up the contents and revision history. For example, there is a special file called .git/description that you can edit and there's even git branch --edit to edit a branch's description. But none of that is useful beyond a local client. That is to say, if you git clone or git push none of that information is published anywhere or made available to anyone else.So Git's "distributed data" is limited to well basically its revision history and series of objects I guess? 🤔
git itself basically just houses some client-side "Metadata" about the repository and a bunch of objects that make up the contents and revision history. For example, there is a special file called .git/description that you can edit and there's even git branch --edit to edit a branch's description. But none of that is useful beyond a local client. That is to say, if you git clone or git push none of that information is published anywhere or made available to anyone else.So Git's "distributed data" is limited to well basically its revision history and series of objects I guess? 🤔
git itself basically just houses some client-side "Metadata" about the repository and a bunch of objects that make up the contents and revision history. For example, there is a special file called .git/description that you can edit and there's even git branch --edit to edit a branch's description. But none of that is useful beyond a local client. That is to say, if you git clone or git push none of that information is published anywhere or made available to anyone else.So Git's "distributed data" is limited to well basically its revision history and series of objects I guess? 🤔
git am - in the right order. It's a bit tedious 🤦♂️
git am - in the right order. It's a bit tedious 🤦♂️
git am - in the right order. It's a bit tedious 🤦♂️
git am - in the right order. It's a bit tedious 🤦♂️
~/.gitconfig "just so" the steps are really just one.
$ git co -b feature
# hack hack hack
$ git ci -m "blah bla hblah"
$ git send-email main
~/.gitconfig "just so" the steps are really just one.
$ git co -b feature
# hack hack hack
$ git ci -m "blah bla hblah"
$ git send-email main
~/.gitconfig "just so" the steps are really just one.
$ git co -b feature
# hack hack hack
$ git ci -m "blah bla hblah"
$ git send-email main
~/.gitconfig "just so" the steps are really just one.
$ git co -b feature
# hack hack hack
$ git ci -m "blah bla hblah"
$ git send-email main
git push to work over SSH so I can have some kind of push + auth support...
git push to work over SSH so I can have some kind of push + auth support...
git push to work over SSH so I can have some kind of push + auth support...
git push to work over SSH so I can have some kind of push + auth support...
git am - -- Hmmm 🤔 -- I _think_ we can do better than this...
git am - -- Hmmm 🤔 -- I _think_ we can do better than this...
git am - -- Hmmm 🤔 -- I _think_ we can do better than this...
git am - -- Hmmm 🤔 -- I _think_ we can do better than this...