From: Jeff King <peff@peff.net>
To: Ilya Basin <basinilya@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: merging bare repository
Date: Fri, 13 May 2011 09:54:12 -0400 [thread overview]
Message-ID: <20110513135412.GA6920@sigill.intra.peff.net> (raw)
In-Reply-To: <533718318.20110513145132@gmail.com>
On Fri, May 13, 2011 at 02:51:32PM +0400, Ilya Basin wrote:
> on server:
> [git@server]$ git clone --bare ssh://git@some.org/git/project.git /git/project.git
>
> on workstation:
> [me@client]$ git clone ssh://git@server/git/project.git
> [me@client]$ cd project
> [me@client]$ touch aaa
> [me@client]$ git add aaa
> [me@client]$ git commit aaa -m abracadabra
> [me@client]$ git push
>
> back on server:
> [git@server]$ git log
> commit e5c871122cadfa4ed4d2ab488852ecdb803b4bd8
> Author: Ilya Basin <>
> Date: Fri May 13 13:39:39 2011 +0400
>
> abracadabra
>
> I want to merge with upstream
> [git@server]$ git fetch
> [git@server]$ git merge origin
> fatal: This operation must be run in a work tree
Yeah, you need a work tree to do a merge, as there may be conflicts.
Moreover, you can't just do the merge via something like cron, as you
may need user intervention to resolve the conflicts.
So from your workstation, you'll want to do:
git remote add upstream ssh://git@some.org/git/project.git
git pull upstream
whenever you feel like merging with upstream.
-Peff
prev parent reply other threads:[~2011-05-13 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 10:51 merging bare repository Ilya Basin
2011-05-13 13:53 ` Magnus Bäck
2011-05-13 20:56 ` Enrico Weigelt
2011-05-31 2:01 ` garyc618
2011-06-06 21:54 ` Magnus Bäck
2011-05-13 13:54 ` Jeff King [this message]
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=20110513135412.GA6920@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=basinilya@gmail.com \
--cc=git@vger.kernel.org \
/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).