Login or Register to Ask a Question and Join Our Community


Software Releases - RSS News

HL7 Comm Multi 0.1.1 (Default branch)

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News HL7 Comm Multi 0.1.1 (Default branch)
# 1  
Old 09-01-2008
HL7 Comm Multi 0.1.1 (Default branch)
HCM is a server version of the widely used HL7Comm integration tool. It is an simple integrationengine designed for the health care industry. Itsupports everything HL7 Comm does, and adds theability to manage and monitor multiple interfacesthrough an easy Web interface.License: GNU General Public License v2Changes:
This is a bugfix release, primarily focused on problems with the interactive logging (the log files themselves were correct). There were also some cosmetic fixes to the log screens.Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT NETBSD

archpath

ARCHPATH(1)						      General Commands Manual						       ARCHPATH(1)

NAME

       archpath - output arch (tla/Bazaar) archive names, with support for branches

SYNOPSIS

       archpath
       archpath branch
       archpath branch--version

DESCRIPTION

       archpath is intended to be run in an arch (tla or Bazaar) working copy.

       In its simplest usage, archpath with no parameters outputs the package name (archive/category--branch--version) associated with the working
       copy.

       If a parameter is given, it may either be a branch--version, in which case archpath will output a corresponding package name in the current
       archive and category, or a plain branch name (without '--"), in which case archpath will output a corresponding package name in the current
       archive and category and with the same version as the current working copy.

       This is useful for branching.  For example, if you're using Bazaar and you want to create a branch for a new feature, you might use a  com-
       mand like this:

	      baz branch $(archpath) $(archpath new-feature)

       Or if you want to tag your current code onto a 'releases' branch as version 1.0, you might use a command like this:

	      baz branch $(archpath) $(archpath releases--1.0)

       That's much easier than using 'baz tree-version' to look up the package name and manually modifying the result.

AUTHOR

       archpath  was  written  by  Colin  Watson  <cjwatson@debian.org>.  Like archpath, this manual page is released under the GNU General Public
       License, version 2 or later.

DEBIAN
								 Debian Utilities						       ARCHPATH(1)