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

Re: Report a bug, about track remote repository.

From
CHCheeray Huang <cheeray.huang@gmail.com>
Date
Oct 21, 2012, 02:44 UTC
Message-ID
<50836175.5020501@gmail.com>
In-Reply-To
<F15116C3B49A439AB06C8068F79E4C0F@PhilipOakley>
On 2012年10月21日 07:46, Philip Oakley wrote:
Show 5 quoted lines
>
> At this point you have created the 'conflict' - You can't have two 
> different branches that both track the same identical remote branch 
> and expect that they can be both different and identical at the same 
> time.
Show 5 quoted lines
> Only one push (from two branches trying) can suceed. You either force 
> the remote to match the current branch, and loose any information that 
> it had about the other branch, or the remote stays with one branch. 
> Simply don't do it [that way]. If the local branches are different, 
> then you need distinct remote branches.

Yes, if it will lead a conflict, I think git should give a warning for it and prevent these operations rather than give a comment to inform you to push something.

-- 
Best Regards!

Qiyu Huang( Cheeray )
Previous: Philip Oakley
Message 3 of 3 in “Report a bug, about track remote repository.”
  1. Cheeray HuangOct 20, 2012
  2. Philip OakleyOct 20, 2012
  3. Cheeray HuangOct 21, 2012

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.