No. A locked file error.

Any work I was doing, was outside the working copy, so nothing should be lost…

On Mar 11, 2013, at 9:24 PM, Om wrote:

> Is the error something about TLF?  If so, there is an easy way to fix it.
> That way you wont lose your work.
> 
> And btw, you could also create a patch from your current work, trash
> working copy and re-apply it to your new workspace.  There is no real
> reason to lose work.
> 
> Om
> 
> On Mon, Mar 11, 2013 at 12:19 PM, Harbs <harbs.li...@gmail.com> wrote:
> 
>> My working copy had errors and refused to update. I trashed the whole
>> thing and I'm checking out a fresh copy. I guess nothing is happening here
>> until tomorrow… :-(
>> 
>> On Mar 11, 2013, at 9:32 AM, Harbs wrote:
>> 
>>> Thanks. That was helpful. My working copy of the repository is not up to
>> date. I'll update later when I get to my office and give it a go.
>>> 
>>> I use Cornerstone for svn. I have no idea how to generate a patch with
>> it, but I'll look into that. All my use of svn has been very basic… ;-)
>>> 
>>> Harbs
>>> 
>>> On Mar 11, 2013, at 9:08 AM, Justin Mclean wrote:
>>> 
>>>> Hi,
>>>> 
>>>>> Can you define "patch"? Do you mean just taking the full .as file and
>> attaching it, or something else?
>>>> Patches are files that describe the differences line by line between
>> two files. SVN can generate patches via "svn patch" on the command line but
>> all SVN tools that I know of have a way of generating patches. For instance
>> subclipse it's right click Team - > Generate Patch.
>>>> 
>>>> Patches can also be generated from a pull request in the ApacheFlex
>> Github mirror and be applied to the current SVN mirror.
>>>> 
>>>> Thanks,
>>>> Justin
>>> 
>> 
>> 

Reply via email to