[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Common name for transaction and revision object

From: Blair Zajac <blair_at_orcaware.com>
Date: Wed, 28 Apr 2010 08:03:33 -0700

On 4/28/10 6:46 AM, Giulio Troccoli wrote:
>>
>
>
> Linedata Services (UK) Ltd
> Registered Office: Bishopsgate Court, 4-12 Norton Folgate, London, E1 6DB
> Registered in England and Wales No 3027851 VAT Reg No 778499447
>
> -----Original Message-----
>
>
>> From: Geoff Rowell [mailto:geoff.rowell_at_gmail.com]
>> Sent: 22 April 2010 14:21
>> To: Giulio Troccoli
>> Cc: users_at_subversion.apache.org
>> Subject: RE: Common name for transaction and revision object
>>
>> Giulio Troccoli<Giulio.Troccoli_at_uk.linedata.com> wrote:
>>>
>>> I'm writing the hooks for a new repository in Perl and I'm
>> exploring
>>> using
>> OO Perl. In both pre- and post-commit hooks I need the list
>> of files, the author and other similar information. My idea
>> was to define a class and create an instance of that class
>> given either the transaction number adn repository path or
>> the revision number and the repository URL. The 'new'
>> function will then initialise all the information I need
>> calling either svnlook or svn. For instance:

>>> As you can see they are almost the same, so it would be
>> nice to have a
>> single class (I could then check the second parameter to see
>> if it's a URL or a path and do things accordingly). But I
>> cannot come up with a single name that would encompass both,
>> and that's what I'm asking the list.
>>>
>>> So, any suggestions?
>>
>
> Sorry, for posting again but I haven't received any suggestions regarding the name. Nobody can come up with anything? Really?

If you look at the svn_fs.h API, they are both referred to as revision roots.
svn_fs_revision_root() and svn_fs_txn_root() both return a svn_fs_root_t * object.

Blair
Received on 2010-04-28 17:04:05 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.