David Barr <davidbarr@xxxxxxxxxx> writes: > I do notice however that the output being fed to sed expands like so: > > commit >634a5f265ad729b91266de65272e2b5a35d05b1c > >634a5f265ad729b91266de65272e2b5a35d05b1c 634a5f2 INSTALL: warn [...] > commit >828ea97de486c1693d6e4f2c7347acb50235a85d > >828ea97de486c1693d6e4f2c7347acb50235a85d 828ea97 Git 1.7.9 > > Maybe the format spec and sed command could use a little tuning. Why would that be a problem, though? The sed script picks only lines that begin with '>' and discards the traditional diff-tree style per commit header, no? -- 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