Moving to git

Yue Liu opuspace at gmail.com
Wed Dec 1 15:08:34 GMT 2010


I think that should be easy. You can just change the working branch of
your local git repo to the working copy version of koffice-essen you
used, then copy all the files you edited from svn working copy to git
working copy, then commit it, then push it to the server and fix the
conflicts.

On Wed, Dec 1, 2010 at 10:47 PM, Thorsten Zachmann <t.zachmann at zagge.de> wrote:
> On Wednesday, December 01, 2010 15:01:30 Ian Monroe wrote:
>> On Wed, Dec 1, 2010 at 2:31 AM, Boudewijn Rempt <boud at valdyas.org> wrote:
>> > On Wednesday 01 December 2010, Cyrille Berger Skott wrote:
>> >> Hi,
>> >>
>> >> Any more thought on the subject ? Anyone has an objection to making the
>> >> git conversion on the 11th of December ? In case there is no comment by
>> >> tonight, I think we can consider to push it to the 11th.
>> >
>> > I wouldn't mind, but I'm kind of torn about it --  I understand why
>> > Thorsten asked for it, but I really want to move to git. Do we already
>> > have the build instructions on community.kde.org, or should we change
>> > them on wiki.koffice.org?
>>
>> Just have it all finished by Friday and we can do it this weekend. :)
>
> Does that mean it is possible to commit to koffice-essen on the weekend without
> interruptions?
> If that is the case I have no problems with that. We should just make sure
> stuff that gets committed to koffice-essen svn branch that weekend will also end
> up in the git repository.
>
> Thorsten
> _______________________________________________
> calligra-devel mailing list
> calligra-devel at kde.org
> https://mail.kde.org/mailman/listinfo/calligra-devel
>



More information about the calligra-devel mailing list