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

Re: How to push properly a la subversion

From
Avery Pennarun <apenwarr@gmail.com>
Date
Jul 29, 2009, 19:12 UTC
Message-ID
<32541b130907291212p2c079cn2d7a8b17693577b4@mail.gmail.com>
In-Reply-To
<4A7095CE.8030307@gmail.com>

On Wed, Jul 29, 2009 at 6:32 PM, Matthieu Stigler<matthieu.stigler@gmail.com> wrote:

Show 9 quoted lines
> I'm discovering git switchig from svn, so I'm still confused... I want
> actually to use git but keeping this idea of one common/public repo that
> different users push/pull from.
>
> I tried just by cloning A to B, changing/commiting B and the pushing to A
> but: then on A the last log is integrated but I have this message with gitk
> "local changes checked in to index but not commited", and those local
>  changes are actually the version of A before the commit from B :-( What I
> expected with svn mentality is that A is changed and updated...

You need to configure A as a "bare" repository. For example: http://toolmantim.com/articles/setting_up_a_new_remote_git_repository

Future versions of git will prevent you from accidentally getting A into the inconsistent state that you've managed to produce.

Avery
Previous: Matthieu StiglerNext: Dmitry Potapov
Message 2 of 7 in “How to push properly a la subversion”
  1. Matthieu StiglerJul 29, 2009
  2. Avery PennarunJul 29, 2009
  3. Dmitry PotapovJul 29, 2009
  4. Dmitry PotapovJul 30, 2009
  5. Matthieu StiglerAug 4, 2009
  6. Dmitry PotapovAug 4, 2009
  7. Nanako ShiraishiAug 4, 2009

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.