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

Re: Pushing a git repository to a new server

From
Ethan Reesor <firelizzard@gmail.com>
Date
Feb 11, 2013, 18:17 UTC
Message-ID
<CAE_TNi=ZN8L=Qy08=UPBi_1sOixJS6qwtKF6o9KFEfTSQnAs5g@mail.gmail.com>
In-Reply-To
<20130211162714.GB16402@sigill.intra.peff.net>

On Mon, Feb 11, 2013 at 11:27 AM, Jeff King <peff@peff.net> wrote: [...]

Show 6 quoted lines
> We talked about this a long time ago. One problem is that it's
> inherently unportable, as the procedure to make a repo is potentially
> different on every server (and certainly that is the case between a
> regular user running stock git and something like GitHub or Google Code;
> I imagine even gitolite has some special procedures for creating repos,
> too).

I was more interested in creating something for my self rather than making any changes to the mainstream git.

Previous: Jeff KingNext: Michael J Gruber
Message 7 of 10 in “Pushing a git repository to a new server”
  1. Ethan ReesorFeb 10, 2013
  2. Konstantin KhomoutovFeb 11, 2013
  3. Ethan ReesorFeb 11, 2013
  4. Konstantin KhomoutovFeb 11, 2013
  5. Ethan ReesorFeb 11, 2013
  6. Jeff KingFeb 11, 2013
  7. Ethan ReesorFeb 11, 2013
  8. Michael J GruberFeb 12, 2013
  9. Jeff KingFeb 12, 2013
  10. Michael J GruberFeb 13, 2013

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.