activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (JIRA)" <j...@apache.org>
Subject [jira] Closed: (AMQNET-55) Patch Collection
Date Wed, 13 Feb 2008 00:30:35 GMT

     [ https://issues.apache.org/activemq/browse/AMQNET-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jim Gomes closed AMQNET-55.
---------------------------

    Resolution: Fixed

All patches have been applied.

> Patch Collection
> ----------------
>
>                 Key: AMQNET-55
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-55
>             Project: ActiveMQ .Net
>          Issue Type: Task
>          Components: ActiveMQ Client, Stomp
>         Environment: Windows XP SP2, .NET 2.0
>            Reporter: Jim Gomes
>            Assignee: James Strachan
>         Attachments: activemq-patch-AMQNET-55.txt
>
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> I have attached the collection of patches for all of my changes.  These changes are made
against revision 571528 of the Subversion trunk repository.  The patch file includes fixes
for the following issues:
> AMQNET-48
> AMQNET-49
> AMQNET-50
> AMQNET-51
> AMQNET-52
> AMQNET-53
> AMQNET-54
> The patchfile was generated from Perforce using the 'p4 diff2 -u' command.  The documentation
from Perforce states that using this option generates a patch-friendly output: "... it uses
the GNU diff -u format.  The file names and dates are in Perforce syntax, but the output seems
digestible by the ubiquitous patch program."
> You may need to perform a minor massage on the filenames in the diff, but it should be
pretty straightforward to get the diff script into shape suitable for automatic patching of
your sources.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message