Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
I got the following errors when I commit the changes: Error: Commit failed (detailed follow): Error: MERGE request failed on 'Support/code/Dev' Error: 'pre-commit' hook failed with error output ************************* Here is the pre-commit file: !/bin/sh REPOS="$1" TXN="$2" SVNLOOK=/usr/bin/svnlook LOGMSG=`$SVNLOOK log -t $TXN $REPOS | grep [a-zA-Z0-9] | wc -c` if [ "$LOGMSG" -lt 5 ]; then echo -e Please provide a meaningful comment when committing changes.. 1>&2 exit 1 fi commit-access-control.pl "$REPOS" "$TXN" commit-access-control.cfg || exit 1 exit 0 Thanks. -DP --- On Wed, 5/27/09, Ben Eisenbraun <bene-Gk2boCrsRs1AfugRpC6u6w at public.gmane.org> wrote: > From: Ben Eisenbraun <bene-Gk2boCrsRs1AfugRpC6u6w at public.gmane.org> > Subject: Re: How to force comments on SVN commit > To: "Dave Peters" <gameslover987-/E1597aS9LQAvxtiuMwx3w at public.gmane.org> > Cc: discuss-mNDKBlG2WHs at public.gmane.org > Date: Wednesday, May 27, 2009, 3:02 PM > On Wed, May 27, 2009 at 11:49:58AM > -0700, Dave Peters wrote: > > Is there a way to force users to provide a comment > when they commit? > > Using a pre-commit hook is the recommended way to do > it.? E.g.: > > http://www.stillnetstudios.com/2008/06/16/require-subversion-comments-minimum/ > > That's just the first hit in google that looked > reasonable.? There are > more. > > -b > > -- > if stupidity got us into this mess; then why cant it get us > out? > ? ? ? ? ? ? ? ? > ? ? ? ? ? ? ? ? > ? ? ? ? ? ? ? ? > ???<will rogers> >
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |