Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <22023652.1189105522373.JavaMail.jira@brutus>
Date: Thu, 6 Sep 2007 12:05:22 -0700 (PDT)
From: "Jim Gomes (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Updated: (AMQNET-55) Patch Collection
In-Reply-To: <27808244.1189105282147.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


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

Jim Gomes updated AMQNET-55:
----------------------------

    Attachment: activemq-patch-AMQNET-55.txt

This incorporates patches to multiple files.  You may need to modify the pathnames inside the patch file before applying it, as they are in Perforce syntax.

> 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.