On 22/01/2009, at 12.51, Greg Stein wrote:
> On Thu, Jan 22, 2009 at 11:36, Jon Bendtsen <jbendtsen_at_laerdal.dk>
> wrote:
>> On 22/01/2009, at 11.30, Greg Stein wrote:
>>> On Thu, Jan 22, 2009 at 11:03, Jon Bendtsen <jbendtsen_at_laerdal.dk>
>>> wrote:
>>>> ...
>>>> But what if people wants more than module, branch, submodule and
>>>> file.
>>>> What about directory and subdir, ...
>>>>
>>>> Maybe we should add generic fields like
>>>> pf1, pf2, ... (Path Field 1, 2, ...)
>>>
>>> That is what I've been trying to describe. You can name each of the
>>> fields as corresponding to a particular path segment:
>>>
>>> headers_from_path = module/branch/submodule/directory/subdir/.../
>>> file
>>
>> yes, but i wanted to add a twist. I didnt want to put the word
>> 'branch'
>> in the header, i figured that a simple pfX could do it
>
> I'm not sure that I understand. You could name the header something
> else like:
>
> headers_from_path = module/myname/.../file
I just wanted to get the headers like this:
/module/branch/submod/directory/subdir/file
X-pf1: module
X-pf2: branch
X-pf3: submod
X-pf4: directory
X-pf5: subdir
X-pf6: file
and for a path like this:
/trunk/module/submod/directory/subdir/file
X-pf1: trunk
X-pf2: module
X-pf3: submod
X-pf4: directory
X-pf5: subdir
X-pf6: file
JonB
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1043140
Received on 2009-01-22 14:05:08 CET