search for: propchanges

Daniel Dunbar wrote: > I'm a bit hesitant to just hack up the installed copy of svnmailer, are we > sure this patch hasn't been dealt with in an upstream version? I don't see that change in the last dev version: http://storage.perlig.de/svnmailer/svnmailer-1.1.0-dev-r1373.tar.bz2 > > -diff_command = /usr/bin/diff -u -L %(label_from)s -L %(label_to)s > > %(from)s

On Fri, Jan 25, 2013 at 2:06 PM, Sebastian Pop <spop at codeaurora.org> wrote: > Sebastian Pop wrote: > > Hi Daniel, > > > > Daniel Dunbar wrote: > > > Hi Sebastion, > > > > > > I've attached the current configuration file from the server. > > > > > > I'm not sure how far you want to go down the "trying to get

...ecame malformed when pushing to trunk svn propedit svn:log --revprop -r 243434 > svn: E175002: DAV request failed; it's possible that the repository's > pre-revprop-change hook either failed or is non-existent > svn: E175002: Repository has not been enabled to accept revision > propchanges; > ask the administrator to create a pre-revprop-change hook > As described here commit messages are not versioned on svn Would it be possible to get a hook made for this http://stackoverflow.com/questions/692851/can-i-go-back-and-edit-comments-on-an-svn-checkin It could be very useful for...

Yup, I didn't either. I went ahead and hacked up a copy with that change and am switching it over now. - Daniel On Fri, Jan 25, 2013 at 3:06 PM, Sebastian Pop <spop at codeaurora.org> wrote: > Daniel Dunbar wrote: > > I'm a bit hesitant to just hack up the installed copy of svnmailer, are > we > > sure this patch hasn't been dealt with in an upstream

...gt; to trunk > > svn propedit svn:log --revprop -r 243434 >> svn: E175002: DAV request failed; it's possible that the repository's >> pre-revprop-change hook either failed or is non-existent >> svn: E175002: Repository has not been enabled to accept revision >> propchanges; >> ask the administrator to create a pre-revprop-change hook >> > > As described here commit messages are not versioned on svn > Would it be possible to get a hook made for this > > http://stackoverflow.com/questions/692851/can-i-go-back-and-edit-comments-on-an-svn-check...

It looks like the Subversion migration is working. The CVS repository is still there, but in read-only mode. However, the SVN repository preserves the version history of the CVS repository, albeit organized slightly differently. For an introduction to Subversion, this online book is essential: http://svnbook.red-bean.com/ It is written by some of the Subversion authors. The only drawback I

Sebastian Pop wrote: > Hi Daniel, > > Daniel Dunbar wrote: > > Hi Sebastion, > > > > I've attached the current configuration file from the server. > > > > I'm not sure how far you want to go down the "trying to get realize nice > > summary path" lines, but if svn_mailer somehow supported running an > > external script to

Hi Daniel, Daniel Dunbar wrote: > Hi Sebastion, > > I've attached the current configuration file from the server. > > I'm not sure how far you want to go down the "trying to get realize nice > summary path" lines, but if svn_mailer somehow supported running an > external script to process the commit and come up with the path that would > be ideal for

Ok, this is done and seems to work. As far as Chris's request for getting "key directory" paths into the commit message, I thought about working on it, but in the end I'm not sure why we shouldn't just encourage people to self-tag their leading commit line with some sort of standard key ([MC], [Target/Mips], whatever). - Daniel On Fri, Jan 25, 2013 at 3:11 PM, Daniel

Dear Duncan, thank you very much. I have been able to use it now, via the following command line: clang -emit-llvm -c -fstack-protector canary.c -o canary.bc llc -print-before=stack-protector -print-after=stack-protector -o canary.s < canary.bc Thank you again, Izabela Maffra. On 26 January 2013 15:55, <llvmdev-request at cs.uiuc.edu> wrote: > Send LLVMdev mailing

...t;> svn propedit svn:log --revprop -r 243434 >>> svn: E175002: DAV request failed; it's possible that the repository's >>> pre-revprop-change hook either failed or is non-existent >>> svn: E175002: Repository has not been enabled to accept revision >>> propchanges; >>> ask the administrator to create a pre-revprop-change hook >>> >> >> As described here commit messages are not versioned on svn >> Would it be possible to get a hook made for this >> >> http://stackoverflow.com/questions/692851/can-i-go-back-and-e...