Johannes Sixt <j.sixt@xxxxxxxxxxxxx> writes: > Johannes Schindelin schrieb: > ... >>> Recently there was a report that \n in the substitution side of s/// is not >>> supported by all seds :-( >> >> Okay, how about replacing the line with >> >> + s/.*/GIT_'$uid'_NAME='\''&'\''\ >> +export GIT_'$uid'_NAME/p >> >> Hmm? (It works here.) > > This looks good. The other case I'm refering to was also solved in this way. That looks ugly to me. Is there a particular reason to force linebreak when a semicolon would do? - 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
