Re: How to discover which files are tagged or branced in a hook script?

2017-12-17 Thread Branko Čibej
On 18.12.2017 08:16, Andreas Krey wrote: > On Sun, 17 Dec 2017 01:22:06 +, Branko ??ibej wrote: > ... >> The /path/ of the file implies which branch or tag it belongs to. There >> is no other information you need. > Oh yes, there is. Knowing which files are included in the tag > is fine (and a

Re: How to discover which files are tagged or branced in a hook script?

2017-12-17 Thread Andreas Krey
On Sun, 17 Dec 2017 01:22:06 +, Branko ??ibej wrote: ... > The /path/ of the file implies which branch or tag it belongs to. There > is no other information you need. Oh yes, there is. Knowing which files are included in the tag is fine (and a very basic property), but I'd also like to be

Re: How to discover which files are tagged or branced in a hook script?

2017-12-17 Thread Andreas Krey
On Mon, 18 Dec 2017 00:35:29 +, Bo Berglund wrote: ... > I have a hard time getting to understand this... > Do you mean that using "trunk", "branches" and "tags" as directories > is entirely voluntary? Exactly. > Does this also mean that files inside a > tags/something directory can be

Re: How to discover which files are tagged or branced in a hook script?

2017-12-17 Thread Nathan Hartman
On Dec 17, 2017, at 6:35 PM, Bo Berglund wrote: > > On Sun, 17 Dec 2017 01:22:06 +0100, Branko ?ibej > wrote: > >> We'll have to dispel some misconceptions. Subversion's data model is >> significantly different from CVS's. Tags (and branches) are not >>

Re: How to discover which files are tagged or branced in a hook script?

2017-12-17 Thread Bo Berglund
On Sun, 17 Dec 2017 01:22:06 +0100, Branko ?ibej wrote: >We'll have to dispel some misconceptions. Subversion's data model is >significantly different from CVS's. Tags (and branches) are not >properties of files, they're just (sub)trees within the repository. >Creating a tag or