From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Sergey Vlasov" <vsu@altlinux.ru>
Cc: "Junio C Hamano" <junkio@cox.net>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Shawn O. Pearce" <spearce@spearce.org>,
git@vger.kernel.org
Subject: Re: [PATCH] More build output cleaning up
Date: Mon, 12 Mar 2007 10:04:00 +0100 [thread overview]
Message-ID: <81b0412b0703120204m2d7a543ep3eec68a580f595ff@mail.gmail.com> (raw)
In-Reply-To: <20070311184827.a98691c3.vsu@altlinux.ru>
On 3/11/07, Sergey Vlasov <vsu@altlinux.ru> wrote:
>
> Using --no-print-directory will break movement to the location of an
> error/warning message at least in vim (emacs will probably have
> problems too), if the error is in some file in a subdirectory. The
You can setup the make command-line to contain -w. It will work
for git and for any other project you may have.
prev parent reply other threads:[~2007-03-12 9:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 23:13 [PATCH] More build output cleaning up Alex Riesen
2007-03-06 23:19 ` Alex Riesen
2007-03-11 15:48 ` Sergey Vlasov
2007-03-12 9:04 ` Alex Riesen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81b0412b0703120204m2d7a543ep3eec68a580f595ff@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=spearce@spearce.org \
--cc=vsu@altlinux.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).