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

Re: git-archimport

From
KGKevin Geiss <kevin@desertsol.com>
Date
Nov 11, 2005, 23:24 UTC
Message-ID
<20051111232428.GS9131@raven.localdomain>
In-Reply-To
<46a038f90511102158k5078e37fn2558cf69bc5794fa@mail.gmail.com>

it's not really public, perhaps I can make it public though. can a tla mirror be served over http? or does it require ssh?

I'm confident the gpg signatures aren't the problem. I imported some branches yesterday which were all signed, they worked fine.

I suspuect the problem is that after tagging the oco branch from the base branch, there are several places where I replayed some patches from one of the branches to the other. some patches were skipped, some were replayed. there was definitely a lot of hard core cherry picking going on, in both directions. do you think that would cause a problem?

the branches I've imported successfully were things where I had version 1, then tagged that to create version 2, then tagged that to create version 3, with no replay or merging going on between the branches. (everything was gpg signed though)

On Fri, Nov 11, 2005 at 06:58:34PM +1300, Martin Langhoff wrote:
Show 10 quoted lines
> On 11/11/05, Kevin Geiss <kevin@desertsol.com> wrote:
> > gpg: Signature made Mon Feb 14 12:28:10 2005 MST using DSA key ID E1E6A3B1
> 
> I've never imported a signed changeset, perhaps that's the problem. Is
> the repo public so I can test it myself?
> 
> cheers,
> 
> martin
>
Previous: Martin LanghoffNext: Martin Langhoff
Message 5 of 6 in “Re: git-archimport”
  1. Kevin GeissNov 10, 2005
  2. Martin LanghoffNov 10, 2005
  3. Kevin GeissNov 11, 2005
  4. Martin LanghoffNov 11, 2005
  5. Kevin GeissNov 11, 2005
  6. Martin LanghoffNov 12, 2005

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.