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

Re: [PATCH] remote-bzr: use proper push method

From
Thomas Rast <trast@inf.ethz.ch>
Date
Apr 25, 2013, 14:50 UTC
Message-ID
<87haiu7jgn.fsf@linux-k42r.v.cablecom.net>
In-Reply-To
<1366889137-19700-1-git-send-email-felipe.contreras@gmail.com>
Felipe Contreras <felipe.contreras@gmail.com> writes:
Show 13 quoted lines
> Not just randomly synchronize the revisions with no checks at all. This
> is the way bazaar's UI does it.
>
> Also, add a non-ff check.
>
> Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
> ---
>
> This patch should probably go to maint, as the results of pushing the way we
> currently push are not really understood. Perhaps it's similar to a 'git push
>  --force', or perhaps it can potentially screw the repository.
>
> It's better to be safe and just do what bazaar does.

Other than "this patch should probably go to maint", this should be in the commit message.

-- 
Thomas Rast
trast@{inf,student}.ethz.ch
Previous: Felipe ContrerasNext: Junio C Hamano
Message 2 of 6 in “remote-bzr: use proper push method”
  1. remote-bzr: use proper push methodFelipe Contreras, Apr 25, 2013
  2. Thomas RastApr 25, 2013
  3. Junio C HamanoApr 25, 2013
  4. Felipe ContrerasApr 25, 2013
  5. Felipe ContrerasApr 25, 2013
  6. Junio C HamanoApr 25, 2013

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.