From: Jakub Narebski <jnareb@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: git@vger.kernel.org
Subject: Re: auto-merge after push?
Date: Mon, 11 May 2009 07:35:45 -0700 (PDT) [thread overview]
Message-ID: <m34ovrn1ww.fsf@localhost.localdomain> (raw)
In-Reply-To: <20090511142326.GA18260@redhat.com>
"Michael S. Tsirkin" <mst@redhat.com> writes:
> Hi!
> I'm working on two machines, and git allows me to switch between them
> and sync by means of git pull. When one machine is behind a firewall, I
> can sometimes only do pushes, but then I have to rememeber to merge when
> I log into remote machine.
>
> Is there a way to trigger merge on remote after push somehow,
> so that running on local machine:
> $ git push remote
> would be equivalent to
> $ ssh remote git pull local
In general this is not possible, because pull can result in merge
conflicts, which you cannot resolve without access. Why not push into
remotes, and when you are on second machine, complete pull by merging
changes? See GitFaq (or GitTips, I don't remember which) where such
approach is described in more detail.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-05-11 14:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 14:23 auto-merge after push? Michael S. Tsirkin
2009-05-11 14:35 ` Jakub Narebski [this message]
2009-05-11 15:18 ` Johannes Schindelin
2009-05-11 20:17 ` Michael S. Tsirkin
2009-05-11 21:03 ` Johannes Schindelin
2009-05-11 21:13 ` Michael S. Tsirkin
2009-05-11 23:29 ` Johannes Schindelin
[not found] ` <20090511211215.GC21045@redhat.com>
2009-05-11 23:28 ` Johannes Schindelin
2009-05-19 9:36 ` Michael S. Tsirkin
2009-06-11 10:40 ` Michael S. Tsirkin
2009-07-11 20:38 ` Michael S. Tsirkin
2009-07-12 2:42 ` Johannes Schindelin
2009-07-12 21:30 ` Junio C Hamano
2009-07-12 22:31 ` Johannes Schindelin
2009-07-15 14:54 ` Michael S. Tsirkin
2009-07-15 19:31 ` Junio C Hamano
2009-07-15 19:57 ` Michael S. Tsirkin
2009-07-16 8:01 ` Johannes Schindelin
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=m34ovrn1ww.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=mst@redhat.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).