Hi Karl,
Karl Berry <[email protected]> writes:
> There were updates to three of the request-* files today that I copy
> from /gd/gnuorg to gnulib. They have trailing whitespace. Can someone
> add these as exceptions instead of bothering the FSF to try to remove
> it? It doesn't hurt anything, so far as I can see. --thanks, karl.
>
> remote: doc/Copyright/request-assign.changes:38: trailing whitespace.
> remote: +[Additional people we should notify about the progress of the
> assignment.]
> remote: doc/Copyright/request-assign.program:35: trailing whitespace.
> remote: +[Additional people we should notify about the progress of the
> assignment.]
> remote: doc/Copyright/request-disclaim.changes:37: trailing whitespace.
>
> remote: +[Additional people we should notify about the progress of the
> assignment.]
> remote: doc/Copyright/request-disclaim.changes:42: new blank line at EOF.
>
> remote: error: hook declined to update refs/heads/master
> To ssh://git.sv.gnu.org/srv/git/gnulib
> ! [remote rejected] master -> master (hook declined)
> error: failed to push some refs to 'ssh://git.sv.gnu.org/srv/git/gnulib'
I think this might be because of the defaults for git's
"core.whitespace" configuration [1], and not something that Gnulib
enforces.
Can you run the following in your Gnulib checkout:
$ git config core.whitespace \
'-blank-at-eol,-blank-at-eof,-trailing-space'
And see if it works then?
Colin
[1]
https://git-scm.com/docs/git-config#Documentation/git-config.txt-corewhitespace
