Gerry:
From: Shaw, Gerry [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 12, 2002 7:18 PM
* Provide a way of doing configuration management (hence the master/
version/ and release/ folders
Why not just use the branch tags provided by CVS rather than bloat
the directory structure?
eg:
So people send in your votes on these topics:
1. propertygroup name=win or property prefix=win
property-group
2. separator attribute or no separator attribute
no separator
---
This sf.net email is sponsored by: OSDN - Tired of that
Done.
-Original Message-
From: Scott Hernandez [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 07, 2003 6:19 PM
To: Jordan, Tom
Cc: [EMAIL PROTECTED]
Subject: Re: [nant-dev] J# compiler tag available for nant
Please send it to the list (compressed please) and we
PM
To: Jordan, Tom
Cc: [EMAIL PROTECTED]
Subject: Re: [nant-dev] J# compiler tag available for nant
Please send it to the list (compressed please) and we will
review it :)
Thanks,
Scott
- Original Message -
From: Jordan, Tom [EMAIL PROTECTED]
To: [EMAIL
Title: Message
Hi
Gius:
Double
check on wether the DocBook stylesheet has
read-only attributes.
I have
run into problems in the past when the stylesheet
has
read-only attributes.
hth,
--
tom.
-Original Message-From: Greco Giuseppe
[mailto:[EMAIL PROTECTED] Sent:
IANAL
If and when, Nant chooses to migrate to a different license,
it will have to handle the copyrights of the contributers.
Scott Hernandez and I briefly discussed this on the Draco.Net
list. Scott wanted references, and I haven't responded because
I had to take some time to look them up.
Hi All:
I am a cvs expert and would like to referr you to the following
branching patterns assembled by Brad, et al:
http://www.cmcrossroads.com/bradapp/acme/branching/
Using these patterns, I have effectively managed projects
in the past. The ones I recommend for CVS are:
Branching Policy:
