Hello, haven't really looked at the commit itself to see what's there, but on the technical side of what you to do, possible options:
1) see: http://stackoverflow.com/questions/12799872/apply-a-commit-chunk-by-chunk - haven't tried it, just found it quickly 2) take the diff of that commit, just add .diff at the end of the link, like: https://github.com/kamailio/kamailio/commit/144737c482d39ae276e8a09f7dea01c5fa685bc6.diff Then you can remove the parts you don't want, apply the resulted patch and commit with: git commit --author="Name <email>" . The value for --author is the value for Author attribute in email notifiication of the initial commit. Cheers, Daniel On 13/11/14 16:09, Charles Chance wrote: > Hi, > > Are there any guidelines/opinions regarding this? > > I would like to cherry pick some of the changes to dmq module from > https://github.com/kamailio/kamailio/commit/144737c482d39ae276e8a09f7dea01c5fa685bc6, > in order to attribute authorship - trouble is, in the same commit > there are changes to files in other modules too. > > Perhaps the simpler approach would be to replicate the changes and > attribute the original author in the new commit message. > > Any advice? > > Cheers, > > Charles > > www.sipcentric.com <http://www.sipcentric.com/> > > Follow us on twitter @sipcentric <http://twitter.com/sipcentric> > > Sipcentric Ltd. Company registered in England & Wales no. > 7365592. Registered office: Faraday Wharf, Innovation Birmingham > Campus, Holt Street, Birmingham Science Park, Birmingham B7 4BB. > > > _______________________________________________ > sr-dev mailing list > [email protected] > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Nov 24-27, Berlin - http://www.asipto.com
_______________________________________________ sr-dev mailing list [email protected] http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
