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

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

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 25, 2013, 22:32 UTC
Message-ID
<7vobd21bt1.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CAMP44s2-QZxuV-bXc_0zeqxJDy=Y6AAC0iwgbjNDNuCaaMcErA@mail.gmail.com>
Felipe Contreras <felipe.contreras@gmail.com> writes:
> My gut feeling is that we should do it the way the Bazaar UI does it,
> I don't have any evidence that there's anything wrong with the current
> code, which Bazaar seems to but have, but for different purposes which
> are hard to explain. I would rather avoid surprises.
That is actually a very fine description for this change ;-).
commit 473b7aac9f542dc22cfff0c264e96d8dbbd9d895
Author: Felipe Contreras <felipe.contreras@gmail.com>
Date:   Thu Apr 25 06:25:37 2013 -0500
    remote-bzr: use proper push method
    
    Do not just randomly synchronize the revisions with no checks at
    all.
    
    I don't have any evidence that there's anything wrong with the
    current code, which Bazaar seems to use, but for different purposes.
    Let's use the logic Bazaar UI uses to avoid surprises.
    
    Also, add a non-ff check.
    
    Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
    Signed-off-by: Junio C Hamano <gitster@pobox.com>
Previous: Felipe Contreras
Message 6 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.