git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: remote-bzr status

From
Sverre Rabbelier <srabbelier@gmail.com>
Date
Oct 7, 2010, 21:27 UTC
Message-ID
<AANLkTi=qmTCX2+Ty5y3FZF5MoK2WrNGFu3Z8rEHv4CzG@mail.gmail.com>
In-Reply-To
<4CABCFDD.4050902@gmail.com>
Heya,
On Wed, Oct 6, 2010 at 03:24, Gabriel Filion <lelutin@gmail.com> wrote:
> I have written a test file that uses test-lib.sh. It is named
> t5801-remote-bzr.sh. I don't know if this name is right so I can correct
> it. I simply took the next sequential number after t5800-remote-helpers.sh.

I also have a t8501-remote-hg.sh, I suppose whoever is done first gets 8501 eh? Easy enough to resolve when the issue arises.

> I've created a clone of git.git [1] in which there's a 'remote-bzr'
> branch. I will be rebasing this branch on top of master and keeping it
> up to date with the other repo's content. (so most operations will be
> non-fastforward pushes)
That's how I've been working too (although I've thrown away the old history).
> Maintaining two repositories will add a little more work but it will
> make it easier for me to post a series on top of git for review and
> possible inclusion later.

You could just drop the non-git repo and work just with the git.git fork (that's what I'm doing), whatever you're comfortable with though.

> So now, most of my work will be to try and fix bzr-fastimport. I tried
> to get in contact with current maintainers of the plugin via Bazaar's
> mailing list but was unsuccessful. I guess I should e-mail Jelmer
> Vernooij directly since he merged some code in not so long ago.

Yes, Jelmer is involved with the bzr fast-import/export stuff, definitely contact him if you haven't already.

-- 
Cheers,

Sverre Rabbelier
Previous: Gabriel Filion
Message 7 of 7 in “remote-bzr status”
  1. Gabriel FilionOct 3, 2010
  2. Sverre RabbelierOct 3, 2010
  3. Jonathan NiederOct 4, 2010
  4. Gabriel FilionOct 4, 2010
  5. Sverre RabbelierOct 4, 2010
  6. Gabriel FilionOct 6, 2010
  7. Sverre RabbelierOct 7, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.