If I understand correctly, you have a ".pbl" file in your repository and
wish to checkout a part of it(?).
As far as subversion is concerned, the .pbl file inside your repository
is a single file. Even if you have a tool to parse the .pbl file, you
will have to checkout the entire file and pipe it to the tool. There is
no shortcut here.
-Arwin Arni
On Wednesday 12 January 2011 02:50 PM, [email protected] wrote:
Hi Sourav,
This is one of the main problems, which we faced six months back. Then
I tried to find out a solution but failed. Now you need to explore it
again.
Regards,
Pabitra Mallick
*From:*SOURAV ROY (WT01 - Manufacturing)
*Sent:* Wednesday, January 12, 2011 2:28 PM
*To:* [email protected]
*Cc:* Sudip Datta (WT01 - Manufacturing); Pabitra Mallick (WT01 -
Manufacturing); Avik Nandi (WT01 - Manufacturing); Amit Sasmal (WT01 -
Manufacturing)
*Subject:* SVN Subversion- object level checkout
Hi team,
We will use Tortoise SVN (Subversion) as version control system or SCM
tool for our project. We are facing an issue for which we would like
to get a solution.
We are linking SVN to Powerbuilder 11.5. We are trying to checkout
files at object level. Every .pbl file, have many files inside. But
SVN is not able to checkout those individual files which are inside
the pbl file. So is there a way by which SVN can checkout those files
which are inside pbl.
TortoiseSVN 1.6.7, 2010/01/22
Subversion 1.6.9
Thanks,
*Sourav Roy **
**Wipro Technologies*
*Please do not print this email unless it is absolutely necessary. *
The information contained in this electronic message and any
attachments to this message are intended for the exclusive use of the
addressee(s) and may contain proprietary, confidential or privileged
information. If you are not the intended recipient, you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately and destroy all copies of this message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient
should check this email and any attachments for the presence of
viruses. The company accepts no liability for any damage caused by any
virus transmitted by this email.
www.wipro.com