Re: copyright issues and derivative work (the case of matlab-mode)

[Uwe Brauer]

>>> "SM" == Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> (I think I can do that in mercurial with the evolve extension and then
>> try to push that locally with the hg-git extension to the local git
>> repository).  That might however mess up things.

> Side note: the current elpa.gnu.org scripts only know how to deal with
> upstream Git repositories.  In theory they might be able to deal with
> a Mercurial upstream using `hg::...`, but I wouldn't bet on it working
> reliably (based on my past experience with the `git-remote-hg` plugin).

In my understanding git-remote-hg is to do things  the other way around:
access a mercurial repository with git. 

It is my understanding from discussions in the mercurial list, however
that this strategy is a lot harder (because mercurial has a lot of
concepts git is lacking, please no flamewar)

I use the hg-git plugin to push and pull to a git repository using
mercurial.

In any case, I put in some security layers (for example for matlab-mode)

    1. I clone with git the repository to my machine (matlab-git)

    2. I locally clone that repository with mercurial (matlab-hg)

    3. I do whatever I do in matlab-hg, then I push to matlab-git

    4. Then I push with git to the matlab repository 

That works quite well. Sometimes I have pushed directly from the
mercurial repository to a sandbox repository in bitbucket and cloned
that repository with git back.

As long as one sticks with mercurial bookmarks that works well. Named
branches are more complicated (one can push them to a git repository and
they will be recognised as git branches, the pulling is more
complicated), but that is now off-topic

smime.p7s
Description: S/MIME cryptographic signature