On Mon, Nov 09, 2009 at 04:53:37PM +0800, Bean wrote:
>
> Hi,
>
> I use the following method to apply patches:
>
> find a common parent for old and new branch.
> move one revision up in old branch,
> remove all files expect .bzr in new branch, then copy files from old branch.
> use bzr commit to
On Mon, Nov 9, 2009 at 4:41 PM, Vladimir 'phcoder' Serbinenko
wrote:
> Bean wrote:
>> On Mon, Nov 9, 2009 at 4:45 AM, Vladimir 'phcoder' Serbinenko
>> wrote:
>>
>>> Bean wrote:
>>>
On Sun, Nov 8, 2009 at 11:36 PM, Vladimir 'phcoder' Serbinenko
wrote:
> Hello, all. As you
Bean wrote:
> On Mon, Nov 9, 2009 at 4:45 AM, Vladimir 'phcoder' Serbinenko
> wrote:
>
>> Bean wrote:
>>
>>> On Sun, Nov 8, 2009 at 11:36 PM, Vladimir 'phcoder' Serbinenko
>>> wrote:
>>>
>>>
Hello, all. As you may have heard or noticed we had a data corruption in
bzr repo
On Mon, Nov 9, 2009 at 4:45 AM, Vladimir 'phcoder' Serbinenko
wrote:
> Bean wrote:
>> On Sun, Nov 8, 2009 at 11:36 PM, Vladimir 'phcoder' Serbinenko
>> wrote:
>>
>>> Hello, all. As you may have heard or noticed we had a data corruption in
>>> bzr repository. We couldn't find for sure what caused
Bean wrote:
> On Sun, Nov 8, 2009 at 11:36 PM, Vladimir 'phcoder' Serbinenko
> wrote:
>
>> Hello, all. As you may have heard or noticed we had a data corruption in
>> bzr repository. We couldn't find for sure what caused it but we could
>> recover it, Robert Millan is running regular backups. B
On Sun, Nov 8, 2009 at 11:36 PM, Vladimir 'phcoder' Serbinenko
wrote:
> Hello, all. As you may have heard or noticed we had a data corruption in
> bzr repository. We couldn't find for sure what caused it but we could
> recover it, Robert Millan is running regular backups. But please be
> careful i
Hello, all. As you may have heard or noticed we had a data corruption in
bzr repository. We couldn't find for sure what caused it but we could
recover it, Robert Millan is running regular backups. But please be
careful in the future.
1) Don't use bzr-svn. The IDs won't match anyway so it's useless.
