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

Re: moving a remote branch?

From
Nazri Ramliy <ayiehere@gmail.com>
Date
Jun 17, 2010, 13:19 UTC
Message-ID
<AANLkTileL-N2Q-90jcxKtQMkaPZob-slGevcorpBHXaj@mail.gmail.com>
In-Reply-To
<A612847CFE53224C91B23E3A5B48BAC74483CEEB16@xmail3.se.axis.com>
On Thu, Jun 17, 2010 at 9:02 PM, Peter Kjellerstedt >
Show 7 quoted lines
> No, you will not (at least not with git 1.7.1 that I use).
>
> Neither do you need to do the two steps below as the two pushes
> above are enough to also keep the status of the remote branches
> in sync in the local repository..
>
> //Peter
Ah, you are right. Thanks for the lesson.
nazri.
Previous: Peter KjellerstedtNext: Thomas Anderson
Message 6 of 8 in “moving a remote branch?”
  1. Thomas AndersonJun 17, 2010
  2. Nazri RamliyJun 17, 2010
  3. Peter KjellerstedtJun 17, 2010
  4. Nazri RamliyJun 17, 2010
  5. Peter KjellerstedtJun 17, 2010
  6. Nazri RamliyJun 17, 2010
  7. Thomas AndersonJun 17, 2010
  8. Peter KjellerstedtJun 17, 2010

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.