{"thread":{"id":"22714","subject":"RFD: git-bzr: anyone interested?","startedAt":"2010-02-18T18:13:44Z","lastAt":"2010-08-07T13:37:41Z","messageCount":30,"participants":["Gabriel Filion","Sverre Rabbelier","Gabriel","Ilari Liusvaara","Felipe Contreras","Chris Packham","Dmitrijs Ledkovs","Miles Bader","Conrad Parker","Jakub Narebski","Matthieu Moy"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"134984","messageId":"4B7D8358.1080108@gmail.com","threadId":"22714","inReplyTo":null,"subject":"RFD: git-bzr: anyone interested?","fromName":"Gabriel Filion","fromEmail":"lelutin@gmail.com","sentAt":"2010-02-18T18:13:44Z","receivedAt":"2010-02-18T18:13:44Z","isPatch":false,"sender":{"key":"lelutin@gmail.com","avatar":"https://avatars.githubusercontent.com/u/108728?v=4"},"body":"Hello,\n\nI started collaborating on a script on github that tries to bring\nbidirectional integration of git with Bazaar repositories. It is the\nscript originally written in ruby by Pieter de Bie and converted to a\nshell script. You can find it here:\n\nhttp://github.com/kfish/git-bzr\n\nThere is probably much left to be done to call this script functional.\nCurrently, it is possible to fetch revisions in a local branch, but I've\nhad problems with pushing revisions.\n\nSo, first things first: in order to make this thing see some substantial\nprogress, I will surely need help from people who are well acquainted\nwith git's internal plumbing, people from git-svn for their valuable\nexperience with extraneous vcs integration and also with people\nacquainted with bzr's inner workings.\n\nIs there any interest from people of this mailing list to see this\nscript make it to a usable state?\nIf so, having some code review would be more than good. What do you\nrecommend on doing: using this mailing list or putting one up that would\nbe specific to the project?\n\n-- \nGabriel Filion\n"},{"id":"134987","messageId":"fabb9a1e1002181037n58d6942dpa63a57a23f506d9c@mail.gmail.com","threadId":"22714","inReplyTo":"4B7D8358.1080108@gmail.com","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Sverre Rabbelier","fromEmail":"srabbelier@gmail.com","sentAt":"2010-02-18T18:37:00Z","receivedAt":"2010-02-18T18:37:00Z","isPatch":false,"sender":{"key":"srabbelier@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3098?v=4"},"body":"Heya,\n\nOn Thu, Feb 18, 2010 at 19:13, Gabriel Filion wrote:\n> Is there any interest from people of this mailing list to see this\n> script make it to a usable state?\n\nWhile I have no interest in bzr, I do have interest in making git\ninterop with more (d)vcs-es. In that light it'd be awesome if instead\nyou created a remote helper instead of 'git-bzr'. By implementing a\nremote helper people can just clone a bzr url, and work with it in the\nexact same way that they would interact with a regular git repository.\nIf you're interested have a look at\nDocumentation/git-remote-helpers.txt, and read the mailing list\narchives on the subject.\n\n> If so, having some code review would be more than good. What do you\n> recommend on doing: using this mailing list or putting one up that would\n> be specific to the project?\n\nDefinitely use the git list if you intend do have it included in\ngit.git, which I think would be a good thing :).\n\n-- \nCheers,\n\nSverre Rabbelier\n"},{"id":"135048","messageId":"4B7E3856.3080609@gmail.com","threadId":"22714","inReplyTo":"fabb9a1e1002181037n58d6942dpa63a57a23f506d9c@mail.gmail.com","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Gabriel Filion","fromEmail":"lelutin@gmail.com","sentAt":"2010-02-19T07:05:58Z","receivedAt":"2010-02-19T07:05:58Z","isPatch":false,"sender":{"key":"lelutin@gmail.com","avatar":"https://avatars.githubusercontent.com/u/108728?v=4"},"body":"On 2010-02-18 13:37, Sverre Rabbelier wrote:\n> By implementing a\n> remote helper people can just clone a bzr url, and work with it in the\n> exact same way that they would interact with a regular git repository.\n\nThis sounds great, it's exactly what I'm hoping to achieve with this\nproject.\n\n> If you're interested have a look at\n> Documentation/git-remote-helpers.txt, and read the mailing list\n> archives on the subject.\n> \n\nThe Documentation/git-remote-helpers.txt file wasn't really of much help\n.. It really only barely scratches the subject, but it does not mention\nhow remote-helpers really work internally (e.g. how do they get called:\nbased on protocol used in URLs?)\n\nI'm still trying to dig up information about how to actually build, test\nand use a remote helper. I'll probably be reading code for examples.\n\nAnother detail hit me: external interaction in git seems like it's\nalmost always using librairies. If I'm not mistaken, bzr does not have a\nseparate library. So to have access to it's API, you need bzr to be\ninstalled. This is why the current git-bzr script is using bzr +\nbzr-fastimport plugin to do the job.\nIs it normal / acceptable for a remote helper to have such dependancies?\n\nAnd for the language used, maybe python could be logical if I can bind\ndirectly to Bazaar's API. Tell me what you think about this.\n\n-- \nGabriel Filion\n"},{"id":"135057","messageId":"fabb9a1e1002182349h923d4acv55d9a41a249d4f51@mail.gmail.com","threadId":"22714","inReplyTo":"4B7E3856.3080609@gmail.com","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Sverre Rabbelier","fromEmail":"srabbelier@gmail.com","sentAt":"2010-02-19T07:49:44Z","receivedAt":"2010-02-19T07:49:44Z","isPatch":false,"sender":{"key":"srabbelier@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3098?v=4"},"body":"Heya,\n\n[please do not cull the cc list, it is considered rude on this list]\n\nOn Fri, Feb 19, 2010 at 08:05, Gabriel Filion wrote:\n> On 2010-02-18 13:37, Sverre Rabbelier wrote:\n>> If you're interested have a look at\n>> Documentation/git-remote-helpers.txt, and read the mailing list\n>> archives on the subject.\n>\n> The Documentation/git-remote-helpers.txt file wasn't really of much help\n> .. It really only barely scratches the subject, but it does not mention\n> how remote-helpers really work internally (e.g. how do they get called:\n> based on protocol used in URLs?)\n\nTrue, I hope to document that better when I submit my git-remote-hg\nimplementation.\n\n> I'm still trying to dig up information about how to actually build, test\n> and use a remote helper. I'll probably be reading code for examples.\n\nPerhaps you could benefit from looking at my git-remote-hg code so\nfar, I'll put it up on github [0] today as 'remote-hg'. If you're too\nsoon you'll see commit 21215675c as the head, which isn't that useful,\nin that case just look again later :P.\n\n> Another detail hit me: external interaction in git seems like it's\n> almost always using librairies. If I'm not mistaken, bzr does not have a\n> separate library. So to have access to it's API, you need bzr to be\n> installed. This is why the current git-bzr script is using bzr +\n> bzr-fastimport plugin to do the job.\n\nThat is part of the reason why the remote-helpers are implemented as\nseparate programs, so that whatever backend they interact with does\nnot become a dependency of git itself.\n\n> Is it normal / acceptable for a remote helper to have such dependancies?\n\nYes, git-remote-hg depends on mercurial being installed.\n\n> And for the language used, maybe python could be logical if I can bind\n> directly to Bazaar's API. Tell me what you think about this.\n\nYup, that would make sense, you could put your code in\n/git_remote_helpers/bzr/, alongside with the to-be-added\n/git_remote_helpers/hg and /git_remote_helpers/cvs.\n\n[0] http://github.com/SRabbelier/git\n\n-- \nCheers,\n\nSverre Rabbelier\n"},{"id":"135075","messageId":"loom.20100219T134421-90@post.gmane.org","threadId":"22714","inReplyTo":"fabb9a1e1002182349h923d4acv55d9a41a249d4f51@mail.gmail.com","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Gabriel","fromEmail":"g2p.code@gmail.com","sentAt":"2010-02-19T12:52:18Z","receivedAt":"2010-02-19T12:52:18Z","isPatch":false,"sender":{"key":"g2p.code@gmail.com","avatar":null},"body":"Sverre Rabbelier writes:\n> > I'm still trying to dig up information about how to actually build, test\n> > and use a remote helper. I'll probably be reading code for examples.\n> \n> Perhaps you could benefit from looking at my git-remote-hg code so\n> far, I'll put it up on github [0] today as 'remote-hg'. If you're too\n> soon you'll see commit 21215675c as the head, which isn't that useful,\n> in that case just look again later :P.\n> \n> [0] http://github.com/SRabbelier/git\n\nFWIW, I'm interested in that remote-vcs code, but never figured out where it\nwas published. TIA for pushing it.\nI'll be using it to better integrate fast-import based backup scripts.\n"},{"id":"135077","messageId":"fabb9a1e1002190538q4600f8c7kb8b2a6345ef3cc33@mail.gmail.com","threadId":"22714","inReplyTo":"loom.20100219T134421-90@post.gmane.org","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Sverre Rabbelier","fromEmail":"srabbelier@gmail.com","sentAt":"2010-02-19T13:38:33Z","receivedAt":"2010-02-19T13:38:33Z","isPatch":false,"sender":{"key":"srabbelier@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3098?v=4"},"body":"Heya,\n\nOn Fri, Feb 19, 2010 at 13:52, Gabriel wrote:\n> FWIW, I'm interested in that remote-vcs code, but never figured out where it\n> was published. TIA for pushing it.\n\nThe remote-helpers code is already in git.git, and has been since git\n1.6.6 with some improvements now in 1.7.0.\n\n> I'll be using it to better integrate fast-import based backup scripts.\n\nDo you mean that you'll write a remote helper to import your backups?\nIf so then my code could be useful as a demonstration on how to hook\nup a fast-import stream.\n\n-- \nCheers,\n\nSverre Rabbelier\n"},{"id":"135079","messageId":"20100219135549.GA31796@Knoppix","threadId":"22714","inReplyTo":"4B7E3856.3080609@gmail.com","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Ilari Liusvaara","fromEmail":"ilari.liusvaara@elisanet.fi","sentAt":"2010-02-19T13:55:49Z","receivedAt":"2010-02-19T13:55:49Z","isPatch":false,"sender":{"key":"ilari.liusvaara@elisanet.fi","avatar":null},"body":"On Fri, Feb 19, 2010 at 02:05:58AM -0500, Gabriel Filion wrote:\n> \n> The Documentation/git-remote-helpers.txt file wasn't really of much help\n> .. It really only barely scratches the subject, but it does not mention\n> how remote-helpers really work internally (e.g. how do they get called:\n> based on protocol used in URLs?)\n> \n> I'm still trying to dig up information about how to actually build, test\n> and use a remote helper. I'll probably be reading code for examples.\n\nThe remote helper is invoked with one or two parameters. \n\nThere are five cases to consider (as rule, first argument is name of\nremote [pseudo-remote in case URL was used] and the second argument is\nURL to use, if any):\n\n1) Remote without URL line but with VCS line value was used.\n\nThe called program: git-remote- [search $PATH for it].\nNumber of arguements: 1\n1st argument: \n\n2) Remote with URL using :: syntax was used.\n\nThe called program: git-remote- [search $PATH for it].\nNumber of arguments: 2\n1st argument: \n2st argument: \n\n3) Remote with URL using :// syntax was used.\n\nThe called program: git-remote- [serch $PATH for it].\nNumber of arguments: 2\n1st argument: \n2st argument: ://\n\n4) URL using :: syntax was used directly on command line.\n\nThe called program: git-remote- [serch $PATH for it].\nNumber of arguments: 2\n1st argument: ::\n2st argument: \n\n5) URL using :// syntax was used directly on command\nline.\n\nThe called program: git-remote- [serch $PATH for it].\nNumber of arguments: 2\n1st argument: ://\n2st argument: ://\n\n\nNotes:\n\n- For 2) and 4), the helper name can only contain alphanumeric characters\n 0-9, A-Z and a-z.\n- For 3) and 5), the helper name can't be any of builtin protocols:\n 'rsync', 'file', 'git', 'ssh', 'git+ssh' nor 'ssh+git'.\n- :: is the strongest, followed by VCS line,\n ::// is weakest.\n\n-Ilari\n"},{"id":"135084","messageId":"20100219161541.272c688f@gmail.com","threadId":"22714","inReplyTo":"fabb9a1e1002190538q4600f8c7kb8b2a6345ef3cc33@mail.gmail.com","subject":"Writing git remote helpers","fromName":"Gabriel","fromEmail":"g2p.code@gmail.com","sentAt":"2010-02-19T15:15:41Z","receivedAt":"2010-02-19T15:15:41Z","isPatch":false,"sender":{"key":"g2p.code@gmail.com","avatar":null},"body":"Sverre Rabbelier:\n> Heya,\n> \n> On Fri, Feb 19, 2010 at 13:52, Gabriel wrote:\n> > FWIW, I'm interested in that remote-vcs code, but never figured out\n> > where it was published. TIA for pushing it.\n> \n> The remote-helpers code is already in git.git, and has been since git\n> 1.6.6 with some improvements now in 1.7.0.\n\nYes, good; I meant I haven't found example uses of that code. I'm aware\nof work on a cvs helper and an hg helper. Users of the python library\nwould be extra convenient.\n\n> > I'll be using it to better integrate fast-import based backup\n> > scripts.\n> \n> Do you mean that you'll write a remote helper to import your backups?\n> If so then my code could be useful as a demonstration on how to hook\n> up a fast-import stream.\n\nI think so.\n\nI'm using fast-import to break down a big json file into a tree, and\nslurp the tree into git. I'm doing this read only. This gives me a\nhistory of the file, compact, human-readable with git log, with an\nincremental remote mirror.\n\nI expect making it work with remote-helpers (I'll need to rebuild json\nfrom the git input to also handle push, I don't know what else is\nrequired) will give me convenient push-pull semantics and I'll be able\nto sync that file across machines, taking advantage of git's merging\nabilities.\nI imagine this kind of sync use case would also work with something\nlike CouchDB or MongoDB, but git has a low barrier to entry for me, and\nI'm not sure how well the others handle tree merging, that sometimes\nrequires human intervention, in a multi-master replication setup.\n\nSpeaking of remote-helpers requirements, besides the fast-import\nstream, what else do I need? I imagine I'll do some book-keeping to\nnote when the current import was last modified (and avoid reimporting\nit when unchanged), and the last hash that was pushed (and avoid\nre-exporting it needlessly).\n\nWhen pushing, how do I tell that the current push is a non\nfast-forward? I can look for the hash of the json file in the history\nof the pushed branch; if it isn't there I'll refuse the push. Do I keep\njson hashes in log messages like git-svn does?\nOr do I store a commit_id -> json hash mapping next to the json file?\nDo I use git notes for that mapping? How do I index back from json hash\nto matching commit to commits having the matching commit in their\nancestry?\n\nWhen pulling, how do I tell there's nothing further to import? Same\napproach as for push: look for the json hash in the history or in a\nlocal mapping, import nothing if found?\n\nThinking about it some more, those two operations need a json_hash ->\ncommit_id lookup followed by a commit_id, commit_id -> bool DAG ancestry\ntest. Is that something the support library provides, or would welcome?\n"},{"id":"135157","messageId":"94a0d4531002200558r70087153i5c43ab669458e817@mail.gmail.com","threadId":"22714","inReplyTo":"4B7D8358.1080108@gmail.com","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2010-02-20T13:58:14Z","receivedAt":"2010-02-20T13:58:14Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"On Thu, Feb 18, 2010 at 8:13 PM, Gabriel Filion wrote:\n> Hello,\n>\n> I started collaborating on a script on github that tries to bring\n> bidirectional integration of git with Bazaar repositories. It is the\n> script originally written in ruby by Pieter de Bie and converted to a\n> shell script. You can find it here:\n>\n> http://github.com/kfish/git-bzr\n>\n> There is probably much left to be done to call this script functional.\n> Currently, it is possible to fetch revisions in a local branch, but I've\n> had problems with pushing revisions.\n>\n> So, first things first: in order to make this thing see some substantial\n> progress, I will surely need help from people who are well acquainted\n> with git's internal plumbing, people from git-svn for their valuable\n> experience with extraneous vcs integration and also with people\n> acquainted with bzr's inner workings.\n>\n> Is there any interest from people of this mailing list to see this\n> script make it to a usable state?\n> If so, having some code review would be more than good. What do you\n> recommend on doing: using this mailing list or putting one up that would\n> be specific to the project?\n\nI'm interested in a tool that's fast (uses git fast-import). Is that planned?\n\n-- \nFelipe Contreras\n"},{"id":"135178","messageId":"4B81EF50.4000409@gmail.com","threadId":"22714","inReplyTo":"94a0d4531002200558r70087153i5c43ab669458e817@mail.gmail.com","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Gabriel Filion","fromEmail":"lelutin@gmail.com","sentAt":"2010-02-22T02:43:28Z","receivedAt":"2010-02-22T02:43:28Z","isPatch":false,"sender":{"key":"lelutin@gmail.com","avatar":"https://avatars.githubusercontent.com/u/108728?v=4"},"body":"On 2010-02-20 08:58, Felipe Contreras wrote:\n> On Thu, Feb 18, 2010 at 8:13 PM, Gabriel Filion wrote:\n>> Hello,\n>>\n>> I started collaborating on a script on github that tries to bring\n>> bidirectional integration of git with Bazaar repositories. It is the\n>> script originally written in ruby by Pieter de Bie and converted to a\n>> shell script. You can find it here:\n>>\n>> http://github.com/kfish/git-bzr\n>>\n>> There is probably much left to be done to call this script functional.\n>> Currently, it is possible to fetch revisions in a local branch, but I've\n>> had problems with pushing revisions.\n>>\n>> So, first things first: in order to make this thing see some substantial\n>> progress, I will surely need help from people who are well acquainted\n>> with git's internal plumbing, people from git-svn for their valuable\n>> experience with extraneous vcs integration and also with people\n>> acquainted with bzr's inner workings.\n>>\n>> Is there any interest from people of this mailing list to see this\n>> script make it to a usable state?\n>> If so, having some code review would be more than good. What do you\n>> recommend on doing: using this mailing list or putting one up that would\n>> be specific to the project?\n> \n> I'm interested in a tool that's fast (uses git fast-import). Is that planned?\n> \nI would like to have as much, but in the context of Bazaar interaction,\nI'm afraid the performance bottleneck will be actually invoking bzr (for\nnow, supposing this is the only way to do things). I'll start work on a\nbzr remote helper shortly and will post a url to my github repos. If you\nwant to help in developing the remote helper and later optimizing its\nperformance, I'll be more than happy about it.\n\n-- \nGabriel Filion\n"},{"id":"135232","messageId":"4B820B4E.7050405@gmail.com","threadId":"22714","inReplyTo":"20100219135549.GA31796@Knoppix","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Gabriel Filion","fromEmail":"lelutin@gmail.com","sentAt":"2010-02-22T04:42:54Z","receivedAt":"2010-02-22T04:42:54Z","isPatch":false,"sender":{"key":"lelutin@gmail.com","avatar":"https://avatars.githubusercontent.com/u/108728?v=4"},"body":"On 2010-02-19 08:55, Ilari Liusvaara wrote:\n> On Fri, Feb 19, 2010 at 02:05:58AM -0500, Gabriel Filion wrote:\n>>\n>> The Documentation/git-remote-helpers.txt file wasn't really of much help\n>> .. It really only barely scratches the subject, but it does not mention\n>> how remote-helpers really work internally (e.g. how do they get called:\n>> based on protocol used in URLs?)\n>>\n>> I'm still trying to dig up information about how to actually build, test\n>> and use a remote helper. I'll probably be reading code for examples.\n> \n> The remote helper is invoked with one or two parameters. \n> \n> There are five cases to consider (as rule, first argument is name of\n> remote [pseudo-remote in case URL was used] and the second argument is\n> URL to use, if any):\n> \n> 1) Remote without URL line but with VCS line value was used.\n> \n> The called program: git-remote- [search $PATH for it].\n> Number of arguements: 1\n> 1st argument: \n> \n> 2) Remote with URL using :: syntax was used.\n> \n> The called program: git-remote- [search $PATH for it].\n> Number of arguments: 2\n> 1st argument: \n> 2st argument: \n> \n> 3) Remote with URL using :// syntax was used.\n> \n> The called program: git-remote- [serch $PATH for it].\n> Number of arguments: 2\n> 1st argument: \n> 2st argument: ://\n> \n> 4) URL using :: syntax was used directly on command line.\n> \n> The called program: git-remote- [serch $PATH for it].\n> Number of arguments: 2\n> 1st argument: ::\n> 2st argument: \n> \n> 5) URL using :// syntax was used directly on command\n> line.\n> \n> The called program: git-remote- [serch $PATH for it].\n> Number of arguments: 2\n> 1st argument: ://\n> 2st argument: ://\n> \n> \n> Notes:\n> \n> - For 2) and 4), the helper name can only contain alphanumeric characters\n> 0-9, A-Z and a-z.\n> - For 3) and 5), the helper name can't be any of builtin protocols:\n> 'rsync', 'file', 'git', 'ssh', 'git+ssh' nor 'ssh+git'.\n> - :: is the strongest, followed by VCS line,\n> ::// is weakest.\n> \n\nThis will prove quite useful! This summary should be inspired upon to\nadd details about how remote helpers are called in the documentation.\n\nI created a dummy remote helper script to test how things are called. I\nwas successful in having a remote created with URL\nbzr://some.server/path to be handed down to the script git-remote-bzr.\n\nHowever, when I tried creating a git-remote-bzr+ssh link pointing to the\ngit-remote-bzr script so that URLs like bzr+ssh://something/somewhere\n(this is how ssh is used with Bazaar) got handed down to the dummy\nscript, it kept saying the \"bzr+ssh\" protocol wasn't handled. So, it\nwould seem I can't have special characters in the helper script name.\n\nHow could I get this protocol to be handled by the remote helper? Having\nto type bzr::bzr+ssh://something/somewhere looks like a really awkward\nthing to write. Also, requiring users to add something to a protocol\nthat already identifies the type of remote repository (and, that is\nalready well known and used by users of bzr) is not interesting in a\nusability point of view.\n\n-- \nGabriel Filion\n"},{"id":"135234","messageId":"4B820DB7.20406@gmail.com","threadId":"22714","inReplyTo":"fabb9a1e1002182349h923d4acv55d9a41a249d4f51@mail.gmail.com","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Gabriel Filion","fromEmail":"lelutin@gmail.com","sentAt":"2010-02-22T04:53:11Z","receivedAt":"2010-02-22T04:53:11Z","isPatch":false,"sender":{"key":"lelutin@gmail.com","avatar":"https://avatars.githubusercontent.com/u/108728?v=4"},"body":"On 2010-02-19 02:49, Sverre Rabbelier wrote:\n> Heya,\n> \n> [please do not cull the cc list, it is considered rude on this list]\n> \nOh .. sorry for that. I will keep this in mind from now on.\n\n> Perhaps you could benefit from looking at my git-remote-hg code so\n> far, I'll put it up on github [0] today as 'remote-hg'.\n> [...]\n> Yup, that would make sense, you could put your code in\n> /git_remote_helpers/bzr/, alongside with the to-be-added\n> /git_remote_helpers/hg and /git_remote_helpers/cvs.\n> \n> [0] http://github.com/SRabbelier/git\n> \nThanks. I'm sure it'll be helpful.\n\nI'm probably not going to push anything in the short future, cause I'd\nlike to experiment a bit and think things through before starting to\ncode. But the bzr remote helper code should be in my git clone on\ngithub. This way interested people can follow along and comment on the\nprogress (more discussions will come on this list)\n\nhttp://github.com/lelutin/git\n\n-- \nGabriel Filion\n"},{"id":"135294","messageId":"20100222105133.GA10577@Knoppix","threadId":"22714","inReplyTo":"4B820B4E.7050405@gmail.com","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Ilari Liusvaara","fromEmail":"ilari.liusvaara@elisanet.fi","sentAt":"2010-02-22T10:51:34Z","receivedAt":"2010-02-22T10:51:34Z","isPatch":false,"sender":{"key":"ilari.liusvaara@elisanet.fi","avatar":null},"body":"On Sun, Feb 21, 2010 at 11:42:54PM -0500, Gabriel Filion wrote:\n> On 2010-02-19 08:55, Ilari Liusvaara wrote:\n \n> However, when I tried creating a git-remote-bzr+ssh link pointing to the\n> git-remote-bzr script so that URLs like bzr+ssh://something/somewhere\n> (this is how ssh is used with Bazaar) got handed down to the dummy\n> script, it kept saying the \"bzr+ssh\" protocol wasn't handled. So, it\n> would seem I can't have special characters in the helper script name.\n\nYeah, it seems like remote helper names can't have non-alphanum characters\n(oops).\n\n> How could I get this protocol to be handled by the remote helper? Having\n> to type bzr::bzr+ssh://something/somewhere looks like a really awkward\n> thing to write. Also, requiring users to add something to a protocol\n> that already identifies the type of remote repository (and, that is\n> already well known and used by users of bzr) is not interesting in a\n> usability point of view.\n\nbzr::ssh://something/somewhere ?\n\nThat goes to git-remote-bzr (as 'ssh://something/somewhere').\n\n-Ilari\n"},{"id":"135392","messageId":"4B834989.50502@gmail.com","threadId":"22714","inReplyTo":"20100222105133.GA10577@Knoppix","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Gabriel Filion","fromEmail":"lelutin@gmail.com","sentAt":"2010-02-23T03:20:41Z","receivedAt":"2010-02-23T03:20:41Z","isPatch":false,"sender":{"key":"lelutin@gmail.com","avatar":"https://avatars.githubusercontent.com/u/108728?v=4"},"body":"On 2010-02-22 05:51, Ilari Liusvaara wrote:\n> bzr::ssh://something/somewhere ?\n> \n> That goes to git-remote-bzr (as 'ssh://something/somewhere').\n> \nThat would be feasible. But for users, when they copy URLs from sites,\nthey'd probably like to use it as is. (I'd like it to be like that :P )\n\nBut, as long as it's not possible right now to use \"+\" in the URL, I can\nimplement it exactly like you said and maybe change it later if helper\nnames obtain the right to have non-alnum characters.\n\n-- \nGabriel Filion\n"},{"id":"135419","messageId":"20100223124553.GA19153@Knoppix","threadId":"22714","inReplyTo":"4B834989.50502@gmail.com","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Ilari Liusvaara","fromEmail":"ilari.liusvaara@elisanet.fi","sentAt":"2010-02-23T12:45:53Z","receivedAt":"2010-02-23T12:45:53Z","isPatch":false,"sender":{"key":"ilari.liusvaara@elisanet.fi","avatar":null},"body":"On Mon, Feb 22, 2010 at 10:20:41PM -0500, Gabriel Filion wrote:\n> On 2010-02-22 05:51, Ilari Liusvaara wrote:\n> > bzr::ssh://something/somewhere ?\n> > \n> > That goes to git-remote-bzr (as 'ssh://something/somewhere').\n> > \n> That would be feasible. But for users, when they copy URLs from sites,\n> they'd probably like to use it as is. (I'd like it to be like that :P )\n> \n> But, as long as it's not possible right now to use \"+\" in the URL, I can\n> implement it exactly like you said and maybe change it later if helper\n> names obtain the right to have non-alnum characters.\n\nPatch to allow '+', '-' and '.' sent (those characters were taken from\nIETF STD66).\n\nIts entierely possible to have remote helpers set up so that in git\nversion that doesn't allow '+', the following work (passed as means\nbeginning of second (URL) argument):\n\n1) 'bzr://' [passed as 'bzr://']\n2) 'bzr::ssh://' [passed as 'ssh://']\n\nAnd in versions that allow '+', the following additionally work:\n\n3) 'bzr+ssh://' [passed as 'bzr+ssh://']\n4) 'ssh+bzr://' [passed as 'ssh+bzr://']\n\nThat can be done by making three copies of executable ('git-remote-bzr',\n'git-remote-bzr+ssh' and 'git-remote-ssh+bzr') and the infering correct\nprotocol from prefix of 2nd arguement (see those \"passed as\" strings).\n\n-Ilari\n"},{"id":"140453","messageId":"p2ka038bef51004261441x7e4857f1mc3f03a4104f8e018@mail.gmail.com","threadId":"22714","inReplyTo":"20100223124553.GA19153@Knoppix","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Chris Packham","fromEmail":"judge.packham@gmail.com","sentAt":"2010-04-26T21:41:59Z","receivedAt":"2010-04-26T21:41:59Z","isPatch":false,"sender":{"key":"judge.packham@gmail.com","avatar":"https://avatars.githubusercontent.com/u/155667?v=4"},"body":"Hi,\n\nHow far did git-bzr or git-remote-bzr get?\n\nI've tried git-bzr from the repo and I seem to be stumbling on bzr not\nhaving the fast-export command after I install the fast-import plugin\nas per [1]. So I think its a bazzar problem not a git-bzr one. Has\nanyone got a fully worked example including the installation of the\nrequired bits and pieces.\n\nAlternatively what I'm really trying to do is update a series of\npatches for an upstream project that is managed with bazzar. We have\n30 or so patches with our customizations so I'd like to get git (or\nbzr) to do the heavy lifting for me. In git I'd do something like this\n\ngit clone \ngit checkout \ngit checkout -b our-patches\ngit am \ngit rebase \ngit format-patch ...\n\nAnybody got a similar recipe for bzr? (yes I'll go ask on the bzr list too)\n\n[1] http://github.com/kfish/git-bzr/blob/master/README\n"},{"id":"140459","messageId":"m2u86ecb3c71004261646zd17cafdcy85cd2ce522a771d5@mail.gmail.com","threadId":"22714","inReplyTo":"p2ka038bef51004261441x7e4857f1mc3f03a4104f8e018@mail.gmail.com","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Dmitrijs Ledkovs","fromEmail":"dmitrij.ledkov@ubuntu.com","sentAt":"2010-04-26T23:46:50Z","receivedAt":"2010-04-26T23:46:50Z","isPatch":false,"sender":{"key":"dmitrij.ledkov@ubuntu.com","avatar":"https://gravatar.com/avatar/79b618c6eb391ddb486c2ee0d3b429014e0e9ba579fd55f2e035f482fc8c24f4?d=mp&s=160"},"body":"On 26 April 2010 22:41, Chris Packham wrote:\n> Hi,\n>\n> How far did git-bzr or git-remote-bzr get?\n>\n\nDon't know, never used.\n\nAs far as I know bzr-git can fetch, clone, commit and push to/from\nbzr/git repos. Not sure why you would want git-bzr\n\n> I've tried git-bzr from the repo and I seem to be stumbling on bzr not\n> having the fast-export command after I install the fast-import plugin\n> as per [1]. So I think its a bazzar problem not a git-bzr one. Has\n> anyone got a fully worked example including the installation of the\n> required bits and pieces.\n>\n\nfast-export would loose information AFAIK use bzr-git with dalwich.\n\n> Alternatively what I'm really trying to do is update a series of\n> patches for an upstream project that is managed with bazzar. We have\n> 30 or so patches with our customizations so I'd like to get git (or\n> bzr) to do the heavy lifting for me. In git I'd do something like this\n>\n> git clone \nbzr branch \n> git checkout \nbzr checkout -rtag: tag-branch\n> git checkout -b our-patches\ncd tag-branch\n> git am \nbzr patch patch1 patch2 patch2\n> git rebase \nbzr rebase ../\n> git format-patch ...\n>\nbzr log -p; or bazaar send -p or create bundle depends on what you want.\n\n> Anybody got a similar recipe for bzr? (yes I'll go ask on the bzr list too)\n>\n\nAlthough I think you really want\nhttp://wiki.bazaar.canonical.com/BzrPipeline which helps you import\npatches ontop of a branch, update upstream, update (merge) patches,\nand export them again. It's something like quilt, topgit but\nbzr-styled ;-)\n\n> [1] http://github.com/kfish/git-bzr/blob/master/README\n\n=) hope this helps.\n\nps. anyone can help with repo.or.cz not reusing objects from parent\nwhen pushing to a fork? reported to admin@repo.or.cz they can\nreproduce the bug but something dodgy is going on. Thanks. Me will\nshut up about bzr now =)\n"},{"id":"140464","messageId":"k2ga038bef51004261758gb75415aq9abe4564b67c25f3@mail.gmail.com","threadId":"22714","inReplyTo":"m2u86ecb3c71004261646zd17cafdcy85cd2ce522a771d5@mail.gmail.com","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Chris Packham","fromEmail":"judge.packham@gmail.com","sentAt":"2010-04-27T00:58:59Z","receivedAt":"2010-04-27T00:58:59Z","isPatch":false,"sender":{"key":"judge.packham@gmail.com","avatar":"https://avatars.githubusercontent.com/u/155667?v=4"},"body":"On Mon, Apr 26, 2010 at 4:46 PM, Dmitrijs Ledkovs\n wrote:\n> On 26 April 2010 22:41, Chris Packham wrote:\n>> Hi,\n>>\n>> How far did git-bzr or git-remote-bzr get?\n>>\n>\n> Don't know, never used.\n>\n> As far as I know bzr-git can fetch, clone, commit and push to/from\n> bzr/git repos. Not sure why you would want git-bzr\n\nBecause I searched the git list and thats what I found. Also because\nI'm familiar with what I want to do using git.\n\n>> I've tried git-bzr from the repo and I seem to be stumbling on bzr not\n>> having the fast-export command after I install the fast-import plugin\n>> as per [1]. So I think its a bazzar problem not a git-bzr one. Has\n>> anyone got a fully worked example including the installation of the\n>> required bits and pieces.\n>>\n>\n> fast-export would loose information AFAIK use bzr-git with dalwich.\n>\n\nI'm not really worried about information loss. As long as I can still\nget at the tags I'm happy. I'm not really planning on keeping this\nrepository after migrating the patches (well may be I'll keep it\naround to submit the changes but I don't think the upstream project\nwould find them interesting anyway).\n\n>> Alternatively what I'm really trying to do is update a series of\n>> patches for an upstream project that is managed with bazzar. We have\n>> 30 or so patches with our customizations so I'd like to get git (or\n>> bzr) to do the heavy lifting for me. In git I'd do something like this\n>>\n>> git clone \n> bzr branch \n>> git checkout \n> bzr checkout -rtag: tag-branch\n>> git checkout -b our-patches\n> cd tag-branch\n>> git am \n> bzr patch patch1 patch2 patch2\n>> git rebase \n> bzr rebase ../\n>> git format-patch ...\n>>\n> bzr log -p; or bazaar send -p or create bundle depends on what you want.\n>\n\nOK heres where I run into problems which I think may be due to\nopenSUSE 11.2s really old version of bzr (1.17). I was missing a 'cd'\nin my example so I'm not sure if there is an implied one in the bzr\nexample. Either way its barfing on 'bzr checkout -rtag:\ntag-branch' and either refuses to work saying that tag-branch is not a\nbranch or crashes with I omit tag-branch.\n\n>> Anybody got a similar recipe for bzr? (yes I'll go ask on the bzr list too)\n>>\n\nexcept the list is subscriber only :( .\n\n> Although I think you really want\n> http://wiki.bazaar.canonical.com/BzrPipeline which helps you import\n> patches ontop of a branch, update upstream, update (merge) patches,\n> and export them again. It's something like quilt, topgit but\n> bzr-styled ;-)\n\nI'll give it a whirl when I've installed a newer version.\n\n> Thanks. Me will shut up about bzr now =)\n>\n\nYeah me too. I should probably bite the bullet and subscribe or import\nthe old and new tarballs and see what git can do with limited\ninformation.\n"},{"id":"140467","messageId":"87wrvtfxx6.fsf@catnip.gol.com","threadId":"22714","inReplyTo":"m2u86ecb3c71004261646zd17cafdcy85cd2ce522a771d5@mail.gmail.com","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Miles Bader","fromEmail":"miles@gnu.org","sentAt":"2010-04-27T02:10:13Z","receivedAt":"2010-04-27T02:10:13Z","isPatch":false,"sender":{"key":"miles@gnu.org","avatar":"https://gravatar.com/avatar/01069b69593af7bff28e2f97afeb3644ae6fe2f5f56cb3a8cf34c5fb8c36efe5?d=mp&s=160"},"body":"Dmitrijs Ledkovs writes:\n> As far as I know bzr-git can fetch, clone, commit and push to/from\n> bzr/git repos. Not sure why you would want git-bzr\n\nIn general people want this because they prefer the\nUI/functionality/speed/etc of the git client over that of the bzr\nclient, but also want to interact with a project that uses a bzr repo.\n\nSo, something like git-bzr is necessary for this (though\n\"git-remote-bzr\" is sounding like it will be the future).\n\nThanks,\n\n-Miles\n\n-- \nWe have met the enemy, and he is us. -- Pogo\n"},{"id":"140469","messageId":"4BD651C6.5050501@gmail.com","threadId":"22714","inReplyTo":"p2ka038bef51004261441x7e4857f1mc3f03a4104f8e018@mail.gmail.com","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Gabriel Filion","fromEmail":"lelutin@gmail.com","sentAt":"2010-04-27T02:53:58Z","receivedAt":"2010-04-27T02:53:58Z","isPatch":false,"sender":{"key":"lelutin@gmail.com","avatar":"https://avatars.githubusercontent.com/u/108728?v=4"},"body":"Hello,\n\nOn 2010-04-26 17:41, Chris Packham wrote:\n> How far did git-bzr or git-remote-bzr get?\n> \n\nI unfortunately haven't had much time to fiddle with this. Having a full\ntime job doesn't give me much space for experiences :( And on my free\ntime, I've been a bit busy with one of my projects..\n\n\nI've tried simply \"plugging in\" the bzr-fastimport plugin to do the\ncommunication part. They already implement output similar to what\ngit-fastimport expects. I was stuck on the part where you have to\nspecify \"marks\" files, and about where to place them, so I left it there\nfor now.\n\nI'll try and work on this pretty soon, but since I'm doing this on spare\ntime, any help would be welcome. Maybe the good thing to do would be to\nput up a page somewhere with a mini-roadmap and the info needed/the info\nthat was found out?\nBy using bzr fast-import, the whole thing shouldn't take too long.\n\n> I've tried git-bzr from the repo and I seem to be stumbling on bzr not\n> having the fast-export command after I install the fast-import plugin\n> as per [1].\n\n> [1] http://github.com/kfish/git-bzr/blob/master/README\n\nThis script needs you to install bazaar and the bzr \"fast-import\"\nplugin. Normally the fast-export command is implemented by it. You need\na rather up-to-date version, though.\nI've found this script to work mostly for pulling in changes from bzr\ninto git. Pushing has proven to be from slow to non-functional.\n\n\nAs for the interest in this: mine is in using only one tool to do the\nwork right and not having to switch from using 3 vcs tools (the current\nsituation at work is 2 -- git and svn -- but soon bzr will come in). And\nfor the one tool, I'd like to choose git.\nstupid reason? probably. but I've tried bzr and I don't like it.\n\n-- \nGabriel Filion\n"},{"id":"140480","messageId":"q2j86ecb3c71004270147le799967dw579964600be84066@mail.gmail.com","threadId":"22714","inReplyTo":"4BD651C6.5050501@gmail.com","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Dmitrijs Ledkovs","fromEmail":"dmitrij.ledkov@ubuntu.com","sentAt":"2010-04-27T08:47:53Z","receivedAt":"2010-04-27T08:47:53Z","isPatch":false,"sender":{"key":"dmitrij.ledkov@ubuntu.com","avatar":"https://gravatar.com/avatar/79b618c6eb391ddb486c2ee0d3b429014e0e9ba579fd55f2e035f482fc8c24f4?d=mp&s=160"},"body":"On 27 April 2010 03:53, Gabriel Filion wrote:\n> Hello,\n>\n> On 2010-04-26 17:41, Chris Packham wrote:\n>> How far did git-bzr or git-remote-bzr get?\n>>\n>\n> I unfortunately haven't had much time to fiddle with this. Having a full\n> time job doesn't give me much space for experiences :( And on my free\n> time, I've been a bit busy with one of my projects..\n>\n>\n> I've tried simply \"plugging in\" the bzr-fastimport plugin to do the\n> communication part. They already implement output similar to what\n> git-fastimport expects. I was stuck on the part where you have to\n> specify \"marks\" files, and about where to place them, so I left it there\n> for now.\n>\n\nExcept that bzr-fast-export -> bzr-fast-import will produce similar\nhistory but all revision ids will be different so you will not be able\nto merge in bzr after you worked in git =/ so it will be read-only.\nMarks files are used when you want to import multiple related bzr\nbranches into a git repo. So in general case you will not need it =)\n\n> I'll try and work on this pretty soon, but since I'm doing this on spare\n> time, any help would be welcome. Maybe the good thing to do would be to\n> put up a page somewhere with a mini-roadmap and the info needed/the info\n> that was found out?\n> By using bzr fast-import, the whole thing shouldn't take too long.\n>\n>> I've tried git-bzr from the repo and I seem to be stumbling on bzr not\n>> having the fast-export command after I install the fast-import plugin\n>> as per [1].\n>\n>> [1] http://github.com/kfish/git-bzr/blob/master/README\n>\n> This script needs you to install bazaar and the bzr \"fast-import\"\n> plugin. Normally the fast-export command is implemented by it. You need\n> a rather up-to-date version, though.\n> I've found this script to work mostly for pulling in changes from bzr\n> into git. Pushing has proven to be from slow to non-functional.\n>\n\nWell I did this:\n\n$ mkdir -p ~/.bazaar/plugins\n$ bzr branch lp:bzr-fast-import ~/.bazaar/fast-import\n$ bzr branch lp:xiphos\n$ git init git-xiphos\n$ cd git-xiphos\n$ bzr fast-export ../xiphos | git fast-import\n\nAnd the resulting git repository has master branch with tags.\n\n>\n> As for the interest in this: mine is in using only one tool to do the\n> work right and not having to switch from using 3 vcs tools (the current\n> situation at work is 2 -- git and svn -- but soon bzr will come in). And\n> for the one tool, I'd like to choose git.\n> stupid reason? probably. but I've tried bzr and I don't like it.\n>\n\nWell I have my stupid reasons as well for choosing bzr for small\nprojects. With bzr-hg, bzr-git & bzr-svn I can work on all 4 without\ndoing a context switch. When I work on something big though like gcc\nor binutils. Yeah git.... because of size & performance.\n\nWith bzr-* plugins though you generally get roundtrip & svn support is\nexcellent. On two machines bzr branch svn://URL will give identical\nbranches which you can merge between in bzr & svn, unlike git where\nyou have to use canonical import to have same SHA-1's on commits.\n\n> --\n> Gabriel Filion\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at  http://vger.kernel.org/majordomo-info.html\n>\n"},{"id":"140526","messageId":"v2ra038bef51004271000u218edd9fp639a53e7d8669345@mail.gmail.com","threadId":"22714","inReplyTo":"q2j86ecb3c71004270147le799967dw579964600be84066@mail.gmail.com","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Chris Packham","fromEmail":"judge.packham@gmail.com","sentAt":"2010-04-27T17:00:39Z","receivedAt":"2010-04-27T17:00:39Z","isPatch":false,"sender":{"key":"judge.packham@gmail.com","avatar":"https://avatars.githubusercontent.com/u/155667?v=4"},"body":"On Tue, Apr 27, 2010 at 1:47 AM, Dmitrijs Ledkovs\n wrote:\n>\n> Well I did this:\n>\n> $ mkdir -p ~/.bazaar/plugins\n> $ bzr branch lp:bzr-fast-import ~/.bazaar/fast-import\n> $ bzr branch lp:xiphos\n> $ git init git-xiphos\n> $ cd git-xiphos\n> $ bzr fast-export ../xiphos | git fast-import\n\nBringing this full circle this is my version of what I needed to do.\nAgain its likely that the old version of bzr that openSUSE uses is the\nreason the above didn't \"just work(tm)\" but just in case anyone else\nis hitting the same problem heres my working recipbzr branch\nlp:bzr-fast-import ~/.bazaar/fast-importe.\n\n# plugin install\nmkdir -p ~/.bazaar/plugins\nbzr branch lp:bzr-fast-import ~/.bazaar/plugins/fastimport # note it\nneeds to be fastimport not fast-import or fast_import\nbzr plugins --verbose # just to check that the plugin is successfully installed\n\n# actual import into git\nbzr branch lp:upstart\ngit init upstart-git\ncd upstart-git/\nbzr fast-export ../upstart | git fast-import\n\n> And the resulting git repository has master branch with tags.\n>\n\nWhich is almost true for me except some tags weren't added due to\n\"missing revisions\", and dang it if it doesn't happen to be the one\nI'm after. This is probably because the 0.5 series for upstart is off\non its own, whatever fixes were in 0.5 probably have been merged I\njust can't tell.\n\nI think for my purposes I can manually find something close enough to\nthe actual revision that I need, either that or mess around trying to\nimport the obsolete 0.5 branch as well but thats something for me to\nwork through on my own now that I've got the fast-export recipe\nworking.\n"},{"id":"140527","messageId":"g2ia038bef51004271013i4e085b31u7ee075bf57bc86a1@mail.gmail.com","threadId":"22714","inReplyTo":"4BD651C6.5050501@gmail.com","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Chris Packham","fromEmail":"judge.packham@gmail.com","sentAt":"2010-04-27T17:13:51Z","receivedAt":"2010-04-27T17:13:51Z","isPatch":false,"sender":{"key":"judge.packham@gmail.com","avatar":"https://avatars.githubusercontent.com/u/155667?v=4"},"body":"On Mon, Apr 26, 2010 at 7:53 PM, Gabriel Filion wrote:\n> Hello,\n>\n> On 2010-04-26 17:41, Chris Packham wrote:\n>> How far did git-bzr or git-remote-bzr get?\n>>\n>\n> I unfortunately haven't had much time to fiddle with this. Having a full\n> time job doesn't give me much space for experiences :( And on my free\n> time, I've been a bit busy with one of my projects..\n\nFair enough. My day job tends to suck up most of the time I want to\nspend in front of a computer too.\n\n> I've tried simply \"plugging in\" the bzr-fastimport plugin to do the\n> communication part. They already implement output similar to what\n> git-fastimport expects. I was stuck on the part where you have to\n> specify \"marks\" files, and about where to place them, so I left it there\n> for now.\n>\n> I'll try and work on this pretty soon, but since I'm doing this on spare\n> time, any help would be welcome. Maybe the good thing to do would be to\n> put up a page somewhere with a mini-roadmap and the info needed/the info\n> that was found out?\n> By using bzr fast-import, the whole thing shouldn't take too long.\n\nI'm probably unqualified to help, not being familiar with bzr at all,\nbut if you want a monkey to write test cases I can probably do that.\n\n>> [1] http://github.com/kfish/git-bzr/blob/master/README\n>\n> This script needs you to install bazaar and the bzr \"fast-import\"\n> plugin. Normally the fast-export command is implemented by it. You need\n> a rather up-to-date version, though.\n> I've found this script to work mostly for pulling in changes from bzr\n> into git. Pushing has proven to be from slow to non-functional.\n\nActually I can probably contribute a snippet for your README file on\nhow to install the required plugin if that would be helpful. It took\nme some fiddling an experimentation to work it out even after reading\nthe bazzar documentation.\n\n> As for the interest in this: mine is in using only one tool to do the\n> work right and not having to switch from using 3 vcs tools (the current\n> situation at work is 2 -- git and svn -- but soon bzr will come in). And\n> for the one tool, I'd like to choose git.\n> stupid reason? probably. but I've tried bzr and I don't like it.\n\nMy interest was purely around updating patches one project that we use\nthat happens to use bazaar. Normally most things we do are either in\ngit or built from tarballs + patches.\n"},{"id":"140557","messageId":"i2o86ecb3c71004271622v115f1f6dp7fbcb5bbdec03cc7@mail.gmail.com","threadId":"22714","inReplyTo":"g2ia038bef51004271013i4e085b31u7ee075bf57bc86a1@mail.gmail.com","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Dmitrijs Ledkovs","fromEmail":"dmitrij.ledkov@ubuntu.com","sentAt":"2010-04-27T23:22:22Z","receivedAt":"2010-04-27T23:22:22Z","isPatch":false,"sender":{"key":"dmitrij.ledkov@ubuntu.com","avatar":"https://gravatar.com/avatar/79b618c6eb391ddb486c2ee0d3b429014e0e9ba579fd55f2e035f482fc8c24f4?d=mp&s=160"},"body":"I don't know if anyone is interested:\n\nI've did the fast-export | import with marks for all release branches\nof upstart.\nSo I have git repo with code since 0.1 series upto the latest 1.0 series.\nI've also committed an update branch which has script to import new revisions.\nI might put it into my crontab for updates.... but small bash script\nis there to update it.\n\nSo far it looks good to me e.g. there is nothing missing what is\npresent in the upstream branches.\n\ngit clone git://gitorious.org/upstart/upstart.git\n\nHappy rebasing ;-)\n"},{"id":"147299","messageId":"AANLkTi=a27OtQX-oNwPqmXDUmZHFyKo+fPZCRgSv04G3@mail.gmail.com","threadId":"22714","inReplyTo":"p2ka038bef51004261441x7e4857f1mc3f03a4104f8e018@mail.gmail.com","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Conrad Parker","fromEmail":"conrad@metadecks.org","sentAt":"2010-08-06T07:19:27Z","receivedAt":"2010-08-06T07:19:27Z","isPatch":false,"sender":{"key":"conrad@metadecks.org","avatar":null},"body":"Hi,\n\nAnyone interested in git-bzr might also want to look at some recent\nrewrites; from the current git-bzr README:\n\nThe following are rewrites in Python and may offer better bzr integration:\n * http://github.com/termie/git-bzr-ng\n * http://github.com/matthew-brett/git-bzr\n\n(... and I'd also be interested to know how well either of these work :)\n\ncheers,\n\nConrad (kfish).\n\nOn 27 April 2010 06:41, Chris Packham wrote:\n> Hi,\n>\n> How far did git-bzr or git-remote-bzr get?\n>\n> I've tried git-bzr from the repo and I seem to be stumbling on bzr not\n> having the fast-export command after I install the fast-import plugin\n> as per [1]. So I think its a bazzar problem not a git-bzr one. Has\n> anyone got a fully worked example including the installation of the\n> required bits and pieces.\n>\n> Alternatively what I'm really trying to do is update a series of\n> patches for an upstream project that is managed with bazzar. We have\n> 30 or so patches with our customizations so I'd like to get git (or\n> bzr) to do the heavy lifting for me. In git I'd do something like this\n>\n> git clone \n> git checkout \n> git checkout -b our-patches\n> git am \n> git rebase \n> git format-patch ...\n>\n> Anybody got a similar recipe for bzr? (yes I'll go ask on the bzr list too)\n>\n> [1] http://github.com/kfish/git-bzr/blob/master/README\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at  http://vger.kernel.org/majordomo-info.html\n>\n>\n"},{"id":"147372","messageId":"8762znjdr0.fsf@catnip.gol.com","threadId":"22714","inReplyTo":"AANLkTi=a27OtQX-oNwPqmXDUmZHFyKo+fPZCRgSv04G3@mail.gmail.com","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Miles Bader","fromEmail":"miles@gnu.org","sentAt":"2010-08-07T03:36:03Z","receivedAt":"2010-08-07T03:36:03Z","isPatch":false,"sender":{"key":"miles@gnu.org","avatar":"https://gravatar.com/avatar/01069b69593af7bff28e2f97afeb3644ae6fe2f5f56cb3a8cf34c5fb8c36efe5?d=mp&s=160"},"body":"Conrad Parker writes:\n> Anyone interested in git-bzr might also want to look at some recent\n> rewrites; from the current git-bzr README:\n>\n> The following are rewrites in Python and may offer better bzr integration:\n> * http://github.com/termie/git-bzr-ng\n> * http://github.com/matthew-brett/git-bzr\n>\n> (... and I'd also be interested to know how well either of these work :)\n\nMe too.\n\nThere are some projects I'd like to work on that have bzr repos, but\nit's always very painful to use the actual bzr client...\n\n-Miles\n\n-- \nChristian, n. One who follows the teachings of Christ so long as they are not\ninconsistent with a life of sin.\n"},{"id":"147381","messageId":"4C5D1DC2.6000704@gmail.com","threadId":"22714","inReplyTo":"8762znjdr0.fsf@catnip.gol.com","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Gabriel Filion","fromEmail":"lelutin@gmail.com","sentAt":"2010-08-07T08:48:02Z","receivedAt":"2010-08-07T08:48:02Z","isPatch":false,"sender":{"key":"lelutin@gmail.com","avatar":"https://avatars.githubusercontent.com/u/108728?v=4"},"body":"(restoring CC list. it is customary on the git list to reply-all)\n\nOn 2010-08-06 23:36, Miles Bader wrote:\n> Conrad Parker writes:\n>> Anyone interested in git-bzr might also want to look at some recent\n>> rewrites; from the current git-bzr README:\n>>\n>> The following are rewrites in Python and may offer better bzr integration:\n>> * http://github.com/termie/git-bzr-ng\n>> * http://github.com/matthew-brett/git-bzr\n>>\n>> (... and I'd also be interested to know how well either of these work :)\n\nI've found some time to begin implementing a remote-helper[1] this week.\nPlugging in a call to \"bzr fast-export\" made cloning a repository with\n\"git clone bzr::url\" and pulling new revisions in with \"git pull\" work\nwith minimum effort.\n\n[1]:http://github.com/lelutin/git-remote-bzr\n\nHowever, as reported in this bug[2], the fast-import path to push\ncommits back to bzr is broken in the bzr plugin. Once we get this\nworking, we should be able to round-trip.\n\n[2]:https://bugs.launchpad.net/bzr-fastimport/+bug/347729\n\nDoing \"git pull\" currently exports all history from the Bazaar branch to\nincorporate the needed commits in the git repo. This is really\nsuboptimal, but I thought having something that works before making it\nwork right would help me get some insights on the remote-helper's code.\n\n\nThe very cool thing about making this into a remote-helper instead of a\ngit command in itself, is that we won't have to redisign (and possibly\nre-implement) the command line interface, since git will be calling the\nremote-helper with the right commands at the appropriate time.\n\n-- \nGabriel Filion\n"},{"id":"147386","messageId":"m3iq3mo9t5.fsf_-_@localhost.localdomain","threadId":"22714","inReplyTo":"AANLkTi=a27OtQX-oNwPqmXDUmZHFyKo+fPZCRgSv04G3@mail.gmail.com","subject":"git-archimport (was: Re: RFD: git-bzr: anyone interested?)","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2010-08-07T13:03:27Z","receivedAt":"2010-08-07T13:03:27Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Conrad Parker writes:\n\n> Anyone interested in git-bzr might also want to look at some recent\n> rewrites; from the current git-bzr README:\n> \n> The following are rewrites in Python and may offer better bzr integration:\n> * http://github.com/termie/git-bzr-ng\n> * http://github.com/matthew-brett/git-bzr\n> \n> (... and I'd also be interested to know how well either of these work :)\n> \n> cheers,\n\nBy the way, perhaps it is time to finally retire git-archimport, or at\nleast move it to contrib section. Is there anyone using it?\n\n-- \nJakub Narebski\nPoland\nShadeHawk on #git\n"},{"id":"147387","messageId":"vpqtyn6h8io.fsf@bauges.imag.fr","threadId":"22714","inReplyTo":"m3iq3mo9t5.fsf_-_@localhost.localdomain","subject":"Re: git-archimport","fromName":"Matthieu Moy","fromEmail":"matthieu.moy@grenoble-inp.fr","sentAt":"2010-08-07T13:11:59Z","receivedAt":"2010-08-07T13:11:59Z","isPatch":false,"sender":{"key":"matthieu.moy@grenoble-inp.fr","avatar":"https://gravatar.com/avatar/72c8a2705971a25dfaff23cece15130d405685845d911aedd5667ace277f3fc5?d=mp&s=160"},"body":"Jakub Narebski writes:\n\n> Conrad Parker writes:\n>\n>> Anyone interested in git-bzr might also want to look at some recent\n>> rewrites; from the current git-bzr README:\n>> \n>> The following are rewrites in Python and may offer better bzr integration:\n>> * http://github.com/termie/git-bzr-ng\n>> * http://github.com/matthew-brett/git-bzr\n>> \n>> (... and I'd also be interested to know how well either of these work :)\n>> \n>> cheers,\n>\n> By the way, perhaps it is time to finally retire git-archimport, or at\n> least move it to contrib section. Is there anyone using it?\n\nDefinitely not using it on a daily basis, but I still have a few GNU\nArch archives on my machine, and may need to import them into Git one\nday.\n\nIf git-archimport causes a problem wrt maintainance, I'd understand\nthat it be deprecated, but if it doesn't cost to keep it around, I\ndon't think it'd be a good thing to drop it.\n\n-- \nMatthieu Moy\nhttp://www-verimag.imag.fr/~moy/\n"},{"id":"147389","messageId":"AANLkTinCn2zozF1cH3PY1yqr3rKdTEMxmP28BofZiTp6@mail.gmail.com","threadId":"22714","inReplyTo":"4C5D1DC2.6000704@gmail.com","subject":"Re: RFD: git-bzr: anyone interested?","fromName":"Miles Bader","fromEmail":"miles@gnu.org","sentAt":"2010-08-07T13:37:41Z","receivedAt":"2010-08-07T13:37:41Z","isPatch":false,"sender":{"key":"miles@gnu.org","avatar":"https://gravatar.com/avatar/01069b69593af7bff28e2f97afeb3644ae6fe2f5f56cb3a8cf34c5fb8c36efe5?d=mp&s=160"},"body":"On Sat, Aug 7, 2010 at 5:48 PM, Gabriel Filion wrote:\n> (restoring CC list. it is customary on the git list to reply-all)\n\nSorry, I was using gmane (mail/news gateway); I'm not totally sure\nwhat it does with replies...\n\nI'll use mail for replies in the future.\n\nThanks,\n\n-Miles\n\n-- \nDo not taunt Happy Fun Ball.\n"}]}