Git apply should be right if you need I can help you On Apr 9, 2012 11:21 PM, "Tony Graziano" <[email protected]> wrote:
> Good question. I could not apply the patch yet either. > > These instructions assume the patch is distributed in unified format, > which identifies the file the patch should be applied to. If not, you can > specify the file on the command line: > > patch foo.txt < bar.patch > > Since it is affecting several files some guidance is warranted, along with > the "unpatch" method to put it back in the event there is an unintended > consequence. > > Perhaps it would be easier if someone were to check in the patch and make > sure it is syntactically correct and provide an RPM to people interested in > testing? > > > On Mon, Apr 9, 2012 at 5:14 PM, Robert Schroeder < > [email protected]> wrote: > > > > I would like to apply this patch to my test server tomorrow. I am not > familiar with the patch process. Would someone mind giving me some > information or help? > > > > > > > > Thanks, > > > > > > > > Rob > > > > > > > > From: [email protected] [mailto: > [email protected]] On Behalf Of Domenico Chierico > > Sent: Thursday, April 05, 2012 7:50 AM > > > > > > To: Discussion list for users of sipXecs software > > Cc: sipXecs developer discussions > > Subject: Re: [sipx-users] [sipx-dev] CDR History Reports Question > > > > > > > > ok here the patch .. I hope it's correct > > > > On Thu, Apr 5, 2012 at 12:15 PM, George Niculae <[email protected]> > wrote: > > > > On Thu, Apr 5, 2012 at 12:44 PM, Domenico Chierico > > <[email protected]> wrote: > > > what i mean is that we can add any filter we need, but i don't think > that a > > > filter that return from "just if it's internal" is conterintuitive. > > > > > > So let me know I can fix patch details as you like and send back to > you. > > > > > > > Tony added a comment to that issue: if this is to be altered, I > > suggest either a tick box to mark it external or internal as part of > > the report output (or both, unless that logic is not functional). > > > > I'd vote for, It looks like the best way to go.. > > > > George > > > > _______________________________________________ > > sipx-users mailing list > > [email protected] > > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > > > > > > > > > > > > ________________________________ > > > NOTICE: This electronic mail message and any content within it are intended > exclusively for the individual(s) or > > > entities to which it is addressed. The message, together with any attachments > and all other content, may contain > > > confidential and/or privileged information. Any unauthorized review, use, > print, save, copy, disclosure or distribution > > > is strictly prohibited. If you have received this message in error, please > immediately advise the sender by reply email > > and delete all copies. > > > > _______________________________________________ > > sipx-users mailing list > > [email protected] > > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > > > > > -- > ~~~~~~~~~~~~~~~~~~ > Tony Graziano, Manager > Telephone: 434.984.8430 > sip: [email protected] > Fax: 434.465.6833 > ~~~~~~~~~~~~~~~~~~ > Linked-In Profile: > http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 > Ask about our Internet Fax services! > ~~~~~~~~~~~~~~~~~~ > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > sip: [email protected].**net<[email protected]> > > Helpdesk Customers: > http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net> > Blog: http://blog.myitdepartment.net > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
