Guten Tag Ahmed, Omair (GE Oil & Gas),
am Freitag, 30. November 2012 um 00:49 schrieben Sie:

> Yes, we have cases where files (in the same path, i.e. trunk/docs)
> are intended for different releases. If as you say, we are doing
> something wrong, what's a better way to handle this? 

> In /trunk/docs:

> Release_doc_1.5
> Release_doc_1.6
> Release_doc_1.7

A more standard way is to combine everything for one release in one
tag or branch or at least create own tags branches for each
docs-release outside the trunk, because in most cases it's unlikely
that all releases in general refer in any way to whatever is in your
trunk.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail:thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/

Telefon...........05151-  9468- 55
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

Reply via email to