bugGNU patch - Bugs: bug #27264, Failure messages should come out...


bug #27264: Failure messages should come out from stderr

Submitted by:  Jari Aalto <jaalto>
Submitted on:  Sun 16 Aug 2009 06:23:35 PM UTC  
Category:  None Severity:  3 - Normal
Item Group:  None Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open

Add a New Comment (Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


Sun 23 Jun 2019 12:40:18 AM UTC, comment #1: 

It's an interesting idea, though I am not sure if this is a good way to divide the output. The patch command already uses stderr for problems internal to the program itself. In other words stderr shows the status of patch itself while stdout displays information regarding the files being worked on.

If problems with the files being worked on are moved to stderr then they will mix with patch's own internal warnings while only "good" reports will print to stdout. That seems more messy rather than less, in my opinion.

This seems like a situation where output should be filtered and divided by existing UNIX utilities rather than by the program itself. Something like "patch -p2 < my.diff | tee all.log | grep FAIL > bad.log"

Follow-up thoughts? Opinions?

Jesse <newguy>
Sun 16 Aug 2009 06:23:35 PM UTC, original submission:  

Cf. http://bugs.debian.org/541855

Package: patch
Version: 2.5.9-5
Severity: minor

It would be helpful if failure messages were displayed on stderr, not stdout to filter the messages

    Hunk #5 FAILED at 220.
    1 out of 6 hunks FAILED -- saving rejects to file arch/sh/kernel/time_32.c.rej

An example:

   patch -p2 < *.diff > good.log 2> bad.log

Jari Aalto <jaalto>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by newguy (Posted a comment)
  • -email is unavailable- added by jaalto (Submitted the item)

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.




    No changes have been made to this item

    Back to the top

    Powered by Savane 3.5