Re: [MirageOS-devel] 2.0 releases going into mirage-dev

[Richard Mortier <Richard.Mortier@xxxxxxxxxxxxxxxx>]

On 3 Nov 2014, at 15:15, Anil Madhavapeddy <anil@xxxxxxxxxx> wrote:

> Interesting question is what we do with mirage-dev now.  Should we instruct 
> people to remove it?  It's actually more useful it seems to have remotes for 
> a specific purpose (mirage/mirage-2-release) so that once they're done, they 
> just contain archives.
> 
> If we bump mirage/mirage-dev to the git versions again, then users will 
> always get the bleeding edge...

+1 to having a set of remotes that act as tags and then keeping mirage-dev as 
the HEAD of everything.

(+10 for adding support to opam for having a repo tag as a remote if it doesn't 
already :) (isn't there some support for accessing branches as remotes with the 
# notation ?)

-- 
Cheers,

R.

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel