Hi, Martin Langhoff wrote:Sure, we certainly need a meta format of some sort (not a full blown VCS, agreed, but somehow we need to represent commits, tags and branches). And IMO, the subversion based format is not a good one, because it treats branches and tags very different from most other systems (and from what it should be from a users perspective: an atomic operation). We (Michael, Oswald and me) have discussed joining efforts of my cvs to monotone converter, but I quickly dropped that idea because the cvs2svn converter is too subversion specific. If cvs2svn wants to become a universal cvs importer, it needs to get rid of those assumptions (and do more work to unify tagging and branching). Regards Markus - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Srivatsa Vaddagiri | containers (was Re: -mm merge plans for 2.6.23) |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Benjamin Herrenschmidt | Re: [PATCH] Remove process freezer from suspend to RAM pathway |
git: | |
| Jarek Poplawski | [PATCH take 2] pkt_sched: Protect gen estimators under est_lock. |
| David Miller | [GIT]: Networking |
| Gerhard Pircher | 3c59x: shared interrupt problem |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
