From: Joel Brobecker <brobecker@adacore.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: ARI/Commit rules
Date: Wed, 15 Jun 2011 15:47:00 -0000 [thread overview]
Message-ID: <20110615154722.GO5944@adacore.com> (raw)
In-Reply-To: <m3k4cnxg0x.fsf@redhat.com>
> It would be nice to fix those warnings eventually. I believe a pre-commit
> hook would only operate on your diffs, though. Anyway we cannot use
> that as the GIT repository is read only. So to me, an ideal thing
> would be just to run it on my files that I have changed, or even better
> a patch I have generated.
There might be one technical issue with processing a diff rather
than the file (I think some regexp match only at the start of
a line), but yeah, that would be much better.
> What do you think?
I think it would be an improvement indeed.
--
Joel
next prev parent reply other threads:[~2011-06-15 15:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 11:56 Phil Muldoon
2011-06-15 15:25 ` Joel Brobecker
2011-06-15 15:37 ` Phil Muldoon
2011-06-15 15:47 ` Joel Brobecker [this message]
2011-06-15 16:39 ` Pedro Alves
2011-06-15 16:48 ` Joel Brobecker
2011-06-15 17:00 ` Pedro Alves
2011-06-15 18:03 ` Alfred M. Szmidt
2011-06-16 11:45 ` Pierre Muller
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=20110615154722.GO5944@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=pmuldoon@redhat.com \
/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