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, 21:11 UTC
Message-ID
<7v1u9y2u4q.fsf@alter.siamese.dyndns.org>
In-Reply-To
<87haiu7jgn.fsf@linux-k42r.v.cablecom.net>
Thomas Rast <trast@inf.ethz.ch> writes:
Show 18 quoted lines
> Felipe Contreras <felipe.contreras@gmail.com> writes:
>
>> 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.
Hmph, should it?

I do not quite understand what "... are not really understood. Perhaps..." wants to say. Understood by whom? By the author of the patch? By the author of the original code?

The log would end up saying "Doing the same as bazaar should be the right thing to do(TM), but don't ask me why. I do not know what I am doing, or why checking is better than not checking, but it seems to work". That _could_ be the truth, but it won't help people who are reading the code later, will it?

Previous: Thomas RastNext: Felipe Contreras
Message 3 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.