[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

  • To: Anil Madhavapeddy <anil@xxxxxxxxxx>
  • From: Richard Mortier <Richard.Mortier@xxxxxxxxxxxxxxxx>
  • Date: Tue, 4 Nov 2014 00:01:07 +0000
  • Accept-language: en-US, en-GB
  • Acceptlanguage: en-US, en-GB
  • Cc: mirageos-devel <mirageos-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 04 Nov 2014 00:01:23 +0000
  • List-id: Developer list for MirageOS <mirageos-devel.lists.xenproject.org>
  • Thread-index: Ac/3wm7+QtlUx3flR6Kw2bag5XZIEw==
  • Thread-topic: [MirageOS-devel] 2.0 releases going into mirage-dev

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 ?)



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

MirageOS-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.