From: martin f krafft <madduck@madduck.net>
To: Fabien Thomas <thomas.fabien@gmail.com>, git@vger.kernel.org
Subject: Re: [topgit] shared topic branch
Date: Mon, 26 Jan 2009 13:00:49 +0100 [thread overview]
Message-ID: <20090126120049.GA9676@lapse.rw.madduck.net> (raw)
In-Reply-To: <EFB70468-7900-4B22-925D-3FC5F05F951B@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
also sprach Fabien Thomas <thomas.fabien@gmail.com> [2008.12.18.2102 +0100]:
> I'm testing topgit 0.5 in a shared env. (multiple user working on same
> patch).
Sorry for the late reply!
> My problem is that when i want to push my local work i'm doing
> "git push" that will force update the remote branch. The problem
> is that each time master is not up to date i will push my entire
> master or topic branch to the remote.
I do not understand what you mean. Could yo please try to give us
more detail? git push is intended to push all local changes to the
remote, so I don't understand what your problem is.
> [remote "origin"]
[...]
> push = +refs/top-bases/*:refs/top-bases/*
> push = +refs/heads/*:refs/heads/*
Those two lines ensure that git pushes all local heads as well as
all top-bases.
--
martin | http://madduck.net/ | http://two.sentenc.es/
it may look like i'm just sitting here doing nothing.
but i'm really actively waiting
for all my problems to go away.
spamtraps: madduck.bogus@madduck.net
[-- Attachment #2: Digital signature (see http://martin-krafft.net/gpg/) --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-27 5:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 20:02 [topgit] shared topic branch Fabien Thomas
2009-01-26 12:00 ` martin f krafft [this message]
2009-01-27 7:23 ` Fabien Thomas
2009-01-30 10:15 ` martin f krafft
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=20090126120049.GA9676@lapse.rw.madduck.net \
--to=madduck@madduck.net \
--cc=git@vger.kernel.org \
--cc=thomas.fabien@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