From: "Yann Droneaud" <ydroneaud@xxxxxxxxxx>
Sent: Tuesday, June 11, 2013 6:06 PM
Hi,
I'm trying to setup a workflow to track vendor releases (upstream).
Each new release are provided as an archive of source code, data,
documentation, etc.
For each vendor releases, fixes need to be applied before making them
available to users (downstream).
Seems to be a rather common use case, ...
Have you looked at the msysgit process that has to cope with upstream
git ;-)
e.g.
https://code.google.com/p/msysgit/source/browse/share/msysGit/merging-rebase.sh?name=python
https://github.com/msysgit/msysgit/blob/master/share/msysGit/merging-rebase.sh
and
https://github.com/msysgit/msysgit/blob/master/share/msysGit/rebasing-merge.sh
whereby the guys re-apply all the patches that haven't been accepted
upstream, along with local fixups to get each new release working.
Philip
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html