Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Samuel Bronson <naesten@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Trailing Whitespace
Date: Fri, 10 Jan 2014 04:00:00 -0000	[thread overview]
Message-ID: <20140110040011.GA4639@adacore.com> (raw)
In-Reply-To: <loom.20140110T042711-984@post.gmane.org>

> > IMHO, better approach is to install on-commit hook blocking commits
> > with trailing whitespace (and tab characters) and leave old code as is.
> 
> Unfortunately, commit hooks have to be set up in every local copy of the
> repository, which I can't see happening.

The best way to do this is to do it on the official repository
(on sourceware) - via the "update" hook.

We can also provide client-side hooks for the "commit", but, as you say,
it would rely on everyone of us activating them.

-- 
Joel


      reply	other threads:[~2014-01-10  4:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-19  0:19 Ben Longbons
2014-01-09 14:45 ` Gary Benson
2014-01-09 14:57   ` Phil Muldoon
2014-01-09 15:01     ` Joel Brobecker
2014-01-09 18:46       ` Dmitry Samersoff
2014-01-10  3:44         ` Samuel Bronson
2014-01-10  4:00           ` Joel Brobecker [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=20140110040011.GA4639@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=naesten@gmail.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