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

Re: Reconstructing git-svn metadata after a git clone

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
May 11, 2010, 13:04 UTC
Message-ID
<AANLkTinZWtMUFtL-Z9gZQQ2pDrPpMooO95l_ylNuD2A9@mail.gmail.com>
In-Reply-To
<AANLkTinMZvBUPPmChwrA1dHr47HXpFldnKH9GO60oIkU@mail.gmail.com>

On Tue, May 11, 2010 at 04:27, Dmitrijs Ledkovs <dmitrij.ledkov@ubuntu.com> wrote:

Show 11 quoted lines
> On 10 May 2010 22:43, Ævar Arnfjörð Bjarmason <avarab@gmail.com> wrote:
>> Why isn't that the case? What info is in .git/svn that can't be
>> inferred from the above?
>>
>
> Is there a git versions mismatch between machine where the first
> import was made and the machine where you are testing bootstrapping by
> any chance?
>
> on my machine I sometimes see "upgrading metadata" when I'm updating
> some of my acient git-svn clones.
No, they were both running 1.7.1 from Debian.
Previous: Dmitrijs Ledkovs
Message 5 of 5 in “Reconstructing git-svn metadata after a git clone”
  1. Ævar Arnfjörð BjarmasonMay 8, 2010
  2. Dmitrijs LedkovsMay 8, 2010
  3. Ævar Arnfjörð BjarmasonMay 10, 2010
  4. Dmitrijs LedkovsMay 11, 2010
  5. Ævar Arnfjörð BjarmasonMay 11, 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.