[prev in list] [next in list] [prev in thread] [next in thread] 

List:       quanta
Subject:    Re: [Quanta] Using FTP without Projects ?
From:       "Mark A. Taff" <mark () marktaff ! com>
Date:       2009-05-26 6:51:22
Message-ID: 206398600905252351v5bc27a57hd51c01b2261e2ca8 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Mon, May 25, 2009 at 4:17 PM, James Ellis <james.ellis@gmail.com> wrote:

> Hi
>
> Thinking laterally.. the bazaar version control system (bazaar-vcs.org)
> has a
> decent plugin called "upload". Basically it connects to a dumb server (i.e
> ftp) and uploads only the changed files in your project automatically with
> one
> command.
> I use it for the projects that only have ftp access. It (like other FTP
> management processes) is not so good if you work in teams as there is still
> the chance to overwrite other team members work (if you work in teams then
> you
> are better off sticking with merging/pulling via SSH within a release
> management system).
>
> For my FTP only projects, the steps are:
> 1. Edit, save etc ... in quanta of course ;)
> 2. bzr add and bzr  commit my changes on the shell
> 3. bzr upload to the dev site
> 4. testing on dev
> 5. bzr upload to the live site.



I use Subversion, as it has a nice interface both on the command line, and
via KDESVN.  Also, I am sure Quanta4 will have built in support for SVN, and
probably git as well, since git is growing in popularity amongst KDE
developers.

I almost exclusively work alone, and even so, I won't write any code without
a version control system.  I even keep everything I write for college in the
Subversion repository.  It make it easy to work on things from any computer.

--Mark

[Attachment #5 (text/html)]

<br><br><div class="gmail_quote">On Mon, May 25, 2009 at 4:17 PM, James Ellis <span \
dir="ltr">&lt;<a href="mailto:james.ellis@gmail.com">james.ellis@gmail.com</a>&gt;</span> \
wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, \
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Hi<br>
<br>
Thinking laterally.. the bazaar version control system (<a \
href="http://bazaar-vcs.org" target="_blank">bazaar-vcs.org</a>) has a<br> decent \
plugin called &quot;upload&quot;. Basically it connects to a dumb server (i.e<br> \
ftp) and uploads only the changed files in your project automatically with one<br> \
command.<br> I use it for the projects that only have ftp access. It (like other \
FTP<br> management processes) is not so good if you work in teams as there is \
still<br> the chance to overwrite other team members work (if you work in teams then \
you<br> are better off sticking with merging/pulling via SSH within a release<br>
management system).<br>
<br>
For my FTP only projects, the steps are:<br>
1. Edit, save etc ... in quanta of course ;)<br>
2. bzr add and bzr   commit my changes on the shell<br>
3. bzr upload to the dev site<br>
4. testing on dev<br>
5. bzr upload to the live site.</blockquote><div><br><br>I use Subversion, as it has \
a nice interface both on the command line, and via KDESVN.   Also, I am sure Quanta4 \
will have built in support for SVN, and probably git as well, since git is growing in \
popularity amongst KDE developers.<br> <br>I almost exclusively work alone, and even \
so, I won&#39;t write any code without a version control system.   I even keep \
everything I write for college in the Subversion repository.   It make it easy to \
work on things from any computer.<br> <br>--Mark<br></div></div>



_______________________________________________
Quanta mailing list
Quanta@mail.kde.org
https://mail.kde.org/mailman/listinfo/quanta


[prev in list] [next in list] [prev in thread] [next in thread]