Source management for open source project with private changes/patches

Neo Jia neojia at gmail.com
Mon Mar 3 17:22:01 CST 2008


thanks. That helps a lot. But I don't want all the team using "qnew"
when they are creating patches. Is there any way to run a script on a
server when people is pushing changes to that repository? And, that
script will turn the changeset to "qnew" patch.

Neo

On Sat, Mar 1, 2008 at 10:40 PM, Dustin Sallings <dustin at spy.net> wrote:
>
>
>
> On Mar 1, 2008, at 22:11, Neo Jia wrote:
> So, I am wondering if there is any way to make this whole process
> automatically. And the ideal way is to make our own private patches to
> the tip of the open source project's branch, so we can provide the
> patches to 3rd party later.
>
> Is there anything I can read? Any suggestions?
>
> BTW, the open source project is using mercurial.
>
>  Good, sounds like you want this, then:
>
>  http://hgbook.red-bean.com/hgbookch12.html
>
> --
> Dustin Sallings
>



-- 
I would remember that if researchers were not ambitious
probably today we haven't the technology we are using!


More information about the Mercurial mailing list