Evan Martin (evan) wrote in evan_tech,
Evan Martin

git inevitability

One of the primary points I was trying to make about git is that it's going to be sort of inevitable in the free software world, so I might as well become proficient with it. And just after that, it turns out two projects I've played with (GnuTLS and reinteract) were both managed with git, and because of my familiarity I've sent patches to both of them.

For what it's worth, here's the process:
  1. hack hack hack
  2. git commit with a useful commit message
  3. repeat steps 1 and 2
  4. Dump your changes as a series of patches: git format-patch origin..
  5. Send them along: git send-email *.patch
I still haven't quite figured out the workflow for re-merging upstream when your patches (or variants) are committed -- maybe you develop in a branch, pull, and diff again to determine whether to throw your branch away? -- so if you have any advice I'm all ears.
Tags: free software, git

  • megaupload captcha

    Someone make a Javascript-based captcha cracker for megaupload. It's strange to see those captchas again because I idly myself wrote a…

  • zombie ghosd

    I was tickled to discover another IBM developerworks article on one of my abandoned hacks and that both it and its predecessor have been translated…

  • gat, a git clone in haskell

    I've been pretty busy with work lately, so I may as well dump this on the internet before it gets too dusty. Though I think I understand Git decently…

  • Post a new comment


    default userpic
    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.