Pushing changes up to the original repository

[Jaime Cham]

Thanks for the great work, we are currently investigating using piston
to manage some common plugins that are shared among various projects.

What is the "proper" and convenient way to push changes made in the
local piston copies of the plugins, back up to the plugin's common
repository? I assume it involves patches, is there a piston-helped way
of generating them? is something like that in the roadmap?

(Forgive me if my newbieness is making me miss something obvious).

Thanks,

Jaime Cham

[François Beausoleil]

Piston has a diff command which should help you with that: http://francois.github.com/piston/diff.html

Not a lot of docs, but try it and see what it gives you.

Hope that helps!
--
François Beausoleil
http://blog.teksol.info/
http://piston.rubyforge.org/

[Jaime Cham]

Hi François, thanks for the response. It seems like diff also gives
you what changed in the remote from the last checkout when what's
really needed to generate a patch is what changed locally (though I
suppose one could first update then diff). Also I don't know if it
makes a difference, but the file pathnames are absolute to the local
system and normally the git-diff ones are relative paths. I shall give
it a try in any case.

Thanks,

Jaime

On Aug 7, 1:52 pm, François Beausoleil <francois.beausol...@gmail.com>
wrote:

> Piston has a diff command which should help you with that:  http://francois.github.com/piston/diff.html
>
> Not a lot of docs, but try it and see what it gives you.
>
> Hope that helps!
> --

> François Beausoleilhttp://blog.teksol.info/http://piston.rubyforge.org/