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

Re: [topgit] shared topic branch

From
MKmartin f krafft <madduck@madduck.net>
Date
Jan 26, 2009, 12:00 UTC
Message-ID
<20090126120049.GA9676@lapse.rw.madduck.net>
In-Reply-To
<EFB70468-7900-4B22-925D-3FC5F05F951B@gmail.com>
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
Previous: Fabien ThomasNext: Fabien Thomas
Message 2 of 4 in “[topgit] shared topic branch”
  1. Fabien ThomasDec 18, 2008
  2. martin f krafftJan 26, 2009
  3. Fabien ThomasJan 27, 2009
  4. martin f krafftJan 30, 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.