On 6/15/2011 6:28 AM, John Arthorne wrote:
> John J Barton
<johnjbarton@xxxxxxxxxxxxxxx>
> I am thinking about using automatic git
branches
to support a
> slightly different work flow in Orion+Firebug. Firebug
will be
> monitoring your changes character at a time. Once Firebug
concludes
> that a patch is syntax correct, the edit would be saved
to the
> server on a new branch. Subsequent changes would be
committed
to
> the branch individually. When the dev pushes "Save"
it really means
> "merge" the auto branch back to the master (or what ever
is current).
Pushing to an SCM on edit/save can certainly be
handy
- we had that in our tools 15 years ago! The only warning I
will give is
that the performance of doing this with Git can be quite bad.
We had something
like this in earlier Orion milestones, where our "file system"
was actually a git repository, and we did add/commit/push on
every editor
save. The performance was terrible, but I suspect with some
work it could
be optimized and/or moved into the background to avoid
disruption.
I guess you where using push to get backup? Perhaps commit (backup
client -> server) is separate from push (backup server ->
remote).
jjb
JohnA
_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev
|
