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

Re: [PATCH v4 2/2] repack: die on incremental + write-bitmap-index

From
Johannes Sixt <j6t@kdbg.org>
Date
Dec 28, 2016, 22:32 UTC
Message-ID
<65a85e09-63ca-48f8-d842-ee8c292d7c2e@kdbg.org>
In-Reply-To
<1482948720-21488-2-git-send-email-dturner@twosigma.com>
Am 28.12.2016 um 19:12 schrieb David Turner:
> +static const char incremental_bitmap_conflict_error[] = N_(
> +"Incremental repacks are incompatible with bitmap indexes.  Use \n"
The SP before LF could be removed.
> +"--no-write-bitmap-index or disable the pack.writebitmaps configuration."
> +);
The string is marked for translation here...
Show 11 quoted lines
> +
> +
>  static int repack_config(const char *var, const char *value, void *cb)
>  {
>  	if (!strcmp(var, "repack.usedeltabaseoffset")) {
> @@ -206,6 +212,9 @@ int cmd_repack(int argc, const char **argv, const char *prefix)
>  	if (pack_kept_objects < 0)
>  		pack_kept_objects = write_bitmaps;
>
> +	if (write_bitmaps && !(pack_everything & ALL_INTO_ONE))
> +		die(incremental_bitmap_conflict_error);
... but then any translations remain unused. This should be
		die(_(incremental_bitmap_conflict_error));
-- Hannes
Previous: David Turner
Message 3 of 3 in “auto gc: don't write bitmaps for incremental repacks”
  1. 1/2 auto gc: don't write bitmaps for incremental repacksDavid Turner, Dec 28, 2016
  2. 2/2 repack: die on incremental + write-bitmap-indexDavid Turner, Dec 28, 2016
  3. Johannes SixtDec 28, 2016

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.