This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH 2/2] allow running mklog as a filter
- From: Yury Gribov <y dot gribov at samsung dot com>
- To: Trevor Saunders <tsaunders at mozilla dot com>
- Cc: gcc-patches at gcc dot gnu dot org, dnovillo at google dot com, Trevor Saunders <tbsaunde at mozilla dot com>
- Date: Tue, 29 Apr 2014 15:59:45 +0400
- Subject: Re: [PATCH 2/2] allow running mklog as a filter
- Authentication-results: sourceware.org; auth=none
- References: <1398737468-6981-1-git-send-email-tsaunders at mozilla dot com> <1398737468-6981-3-git-send-email-tsaunders at mozilla dot com> <535F362F dot 10700 at samsung dot com> <20140429101611 dot GB6192 at tsaunders-iceball dot corp dot tor1 dot mozilla dot com>
I agree stdin gets different semantics than other files but I think
that's sort of ok because it means you generated the patch somehow so
presumably you can do that again if you need the patch.
True but this would be a surpising behavior for ordinary Linux user. We
can wait for Diego's opinion.
Writing the
diff to stdout seems possible, but atleast for my use cases its
annoying, but I guess I'm open to adding a flag or something.
You could pipe output through sed or something to extract CL-part:
$ mklog ... | sed -ne '/^diff --git/q; p'
-Y