Love the illustrations though. 😍
~/.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
main will include your diff from the branch feature?
main will include your dog from the branch feature?
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 🤦♂️
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 🤔
format-patch numbers your patches so that you can apply them with an one liner, no matter if they're 1 or 9999. As for identity leakage, do notice that only author patch info is present - a name (that can be a pseudonym) and an address field that can be empty. Other then that you only have the transport means, but you don't really need to use e-mail if that is your concern, you can for eg. set up an anonymous ftp... you just need to get the formatted patches, git not having its own transport is not a limitation but the freedom to let you get patches in any way you want! ;-)
format-patch numbers your patches so that you can apply them with an one liner, no matter if they're 1 or 9999. As for identity leakage, do notice that only author patch info is present - a name (that can be a pseudonym) and an address field that can be empty. Other then that you only have the transport means, but you don't really need to use e-mail if that is your concern, you can for eg. set up an anonymous ftp... you just need to get the formatted patches, git not having its own transport is not a limitation but the freedom to let you get patches in any way you want! ;-)
git log --pretty=twtxt that someone can get for every branch of every repo on your new git web interface?
git log --pretty=twtxt that someone can get for every branch of every repo on your new git web interface?
That's right...