Re: PostgreSQL Developer meeting minutes up

On 6/3/09, Aidan Van Dyk <aidan@highrise.ca> wrote:
> * Marko Kreen <markokr@gmail.com> [090603 10:26]:
>  > Thats true, but it's not representable in VCS, unless you use cherry-pick,
>  > which is just UI around patch transport.  But considering separate
>  > local trees (with can optionally contain local per-fix branches),
>  > it is possible to separate the fix-developement from final representation.
>
>
> I'll note that in git, cherry-pick is *more* than just "patch
>  transport".  I would more call it "patch commute".  It does actually
>  look at the history between the "pick"ed patch, and the current
>  tree, any merge/fork points, and the differences on each path that lead
>  to the changes in the current tree and the picked patch.

Well, thats good to know, but this also seems to mean it's rather bad
tool for back-patching, as you risk including random unwanted commits
too that happened in the HEAD meantime.  But also, it's very good
tool for forward-patching.

But my point was not about that - rather I was pointing out that
this "patch-commute" will result in duplicate commits, that have
no ties in DAG.

-- 
marko