From: Avery Pennarun <apenwarr@gmail.com>
To: Matthieu Stigler <matthieu.stigler@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: How to push properly a la subversion
Date: Wed, 29 Jul 2009 19:12:32 +0000 [thread overview]
Message-ID: <32541b130907291212p2c079cn2d7a8b17693577b4@mail.gmail.com> (raw)
In-Reply-To: <4A7095CE.8030307@gmail.com>
On Wed, Jul 29, 2009 at 6:32 PM, Matthieu
Stigler<matthieu.stigler@gmail.com> wrote:
> 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
next prev parent reply other threads:[~2009-07-29 19:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 18:32 How to push properly a la subversion Matthieu Stigler
2009-07-29 19:12 ` Avery Pennarun [this message]
2009-07-29 19:50 ` Dmitry Potapov
[not found] ` <111060c20907300111u4345b1f1x784229c066fb3f88@mail.gmail.com>
2009-07-30 11:54 ` Dmitry Potapov
2009-08-04 7:17 ` Matthieu Stigler
2009-08-04 12:04 ` Dmitry Potapov
2009-08-04 21:15 ` Nanako Shiraishi
-- strict thread matches above, loose matches on Subject: below --
2009-07-30 10:11 Matthieu Stigler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=32541b130907291212p2c079cn2d7a8b17693577b4@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=matthieu.stigler@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).