On Sun, Jun 09, 2013 at 11:40:43AM -0500, Felipe Contreras wrote: > - git_am_opt="$git_am_opt -q" This one makes me wonder a bit. I'm not sure about how this works in git, so I would appriciate if someone can explain. I might also have misunderstood something. Here we have two sh-scripts (git rebase and git am) interacting witch eachother. Both uses GIT_QUIET, so if GIT_QUIET already is set by the caller (git rebase) the callee doesn't have to set it to. However GIT_QUIET is undocumented for git-am (in Git Manual). If we translate git am to C/ruby/python/perl/etc. will we catch this? This raises a few more generall questions: do we already pass information between processes(!) with enviroment variables? And is this documented the way it should be? -- Med vänliga hälsningar Fredrik Gustafsson tel: 0733-608274 e-post: iveqy@xxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html