git-subtree: Avoid using echo -n even indirectly #61
Conversation
Since say uses echo, this uses echo -n, which is not portable - see 19c3c5f. Without this commit, the output looks like: ... -n 1891/ 1936 (1883) -n 1892/ 1936 (1884) -n 1893/ 1936 (1885) ... Signed-off-by: Paolo G. Giarrusso <p.giarrusso@gmail.com>
|
I'll close this myself when I'll be aware the patch has been merged. |
|
@Blaisorblade If you wish to submit a patch please follow the instructions in Documentation/SubmittingPatches. All Git integration happens on the mailinglist. |
|
@n1xim I read the instructions, thus I wrote:
I could have added a link to the thread. Here it is: BTW, since the patch still merges, it seems clear that no action was taken. Update: luckily, this entry tracks the fact that the patch is not merged. Is there any other bug tracker? If so, I'd be happy to use it. If not (and it does not seem to be the case), I think you should have one. |
Please close the request.@Blaisorblade
So that's your bug tracker. |
|
I contend a ML implements no feature of a bug tracker. Closing this anyway. |
fixup! Silence GCC's "cast of pointer to integer of a different size" warning
Since say uses echo, this uses echo -n, which is not portable - see
19c3c5f.
Without this commit, the output looks like:
Signed-off-by: Paolo G. Giarrusso p.giarrusso@gmail.com
I am submitting this patch by email as requested; however, email is an inferior tracker interface compared to pull requests, at least for me. This pull request allows me to track this patch.