Re: [PATCH 1/6] t3404 & t3411: undo copy&paste

Johannes Schindelin [off-list ref] writes:

quoted

quoted

+		sed -n "${line}p" < "$1".tmp
+		sed -n "${line}s/^pick/$action/p" < "$1".tmp >> "$1"
+		sed -n "${line}s/^pick/$action/p" < "$1".tmp

Probably.  It is for debugging, anyway.  As everything you only see with 
-v.

Exactly.  That is why I'd rather want to see what exact insn sequence is
being fed to the "rebase -i".  Because I'd be debugging my new test or
changes to "rebase -i", not debugging fake-editor's use of sed.

Hi,

On Tue, 27 Jan 2009, Junio C Hamano wrote:

Johannes Schindelin [off-list ref] writes:

quoted

quoted

quoted

+		sed -n "${line}p" < "$1".tmp
+		sed -n "${line}s/^pick/$action/p" < "$1".tmp >> "$1"
+		sed -n "${line}s/^pick/$action/p" < "$1".tmp

Probably.  It is for debugging, anyway.  As everything you only see with 
-v.

Exactly.  That is why I'd rather want to see what exact insn sequence is 
being fed to the "rebase -i".  Because I'd be debugging my new test or 
changes to "rebase -i", not debugging fake-editor's use of sed.

If you are really after seeing the constructed rebase script, then

			tail -n 1 "$1"

would make tons more sense, no?

Ciao,
Dscho