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

Re: [PATCH 07/12] ll-merge: make flag easier to populate

From
Bert Wesarg <bert.wesarg@googlemail.com>
Date
Aug 5, 2010, 12:12 UTC
Message-ID
<AANLkTi=9GwZgiQHpBLN_L14==Pir0Gs=DosZHF4wg9zi@mail.gmail.com>
In-Reply-To
<20100805111738.GI13779@burratino>
On Thu, Aug 5, 2010 at 13:17, Jonathan Nieder <jrnieder@gmail.com> wrote:
Show 109 quoted lines
> ll_merge() takes its options in a flag word, which has a few
> advantages:
>
>  - options flags can be cheaply passed around in registers, while
>   an option struct passed by pointer cannot;
>
>  - callers can easily pass 0 without trouble for no options,
>   while an option struct passed by value would not allow that.
>
> The downside is that code to populate and access the flag word can be
> somewhat opaque.  Mitigate that with a few macros.
>
> Cc: Avery Pennarun <apenwarr@gmail.com>
> Cc: Bert Wesarg <bert.wesarg@googlemail.com>
> Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
> ---
>  Documentation/technical/api-merge.txt |   11 +++++++----
>  ll-merge.c                            |    9 +++++----
>  ll-merge.h                            |   14 ++++++++++++++
>  merge-recursive.c                     |    3 ++-
>  4 files changed, 28 insertions(+), 9 deletions(-)
>
> diff --git a/Documentation/technical/api-merge.txt b/Documentation/technical/api-merge.txt
> index 01a89d6..a7e050b 100644
> --- a/Documentation/technical/api-merge.txt
> +++ b/Documentation/technical/api-merge.txt
> @@ -49,12 +49,15 @@ supports this.
>
>  The `flag` parameter is a bitfield:
>
> - - The least significant bit indicates whether this is an internal
> -   merge to consolidate ancestors for a recursive merge.
> + - The `LL_OPT_VIRTUAL_ANCESTOR` bit indicates whether this is an
> +   internal merge to consolidate ancestors for a recursive merge.
>
> - - The next two bits allow local conflicts to be automatically
> + - The `LL_OPT_FAVOR_MASK` bits allow local conflicts to be automatically
>    resolved in favor of one side or the other (as in 'git merge-file'
> -   `--ours`/`--theirs`/`--union` for 01, 10, and 11, respectively).
> +   `--ours`/`--theirs`/`--union`).
> +   They can be populated by `create_ll_flag`, whose argument can be
> +   `XDL_MERGE_FAVOR_OURS`, `XDL_MERGE_FAVOR_THEIRS`, or
> +   `XDL_MERGE_FAVOR_UNION`.
>
>  Everything else
>  ---------------
> diff --git a/ll-merge.c b/ll-merge.c
> index 5068fe0..290f764 100644
> --- a/ll-merge.c
> +++ b/ll-merge.c
> @@ -46,7 +46,7 @@ static int ll_binary_merge(const struct ll_merge_driver *drv_unused,
>         * or common ancestor for an internal merge.  Still return
>         * "conflicted merge" status.
>         */
> -       mmfile_t *stolen = (flag & 01) ? orig : src1;
> +       mmfile_t *stolen = (flag & LL_OPT_VIRTUAL_ANCESTOR) ? orig : src1;
>
>        result->ptr = stolen->ptr;
>        result->size = stolen->size;
> @@ -79,7 +79,7 @@ static int ll_xdl_merge(const struct ll_merge_driver *drv_unused,
>
>        memset(&xmp, 0, sizeof(xmp));
>        xmp.level = XDL_MERGE_ZEALOUS;
> -       xmp.favor= (flag >> 1) & 03;
> +       xmp.favor = ll_opt_favor(flag);
>        if (git_xmerge_style >= 0)
>                xmp.style = git_xmerge_style;
>        if (marker_size > 0)
> @@ -99,7 +99,8 @@ static int ll_union_merge(const struct ll_merge_driver *drv_unused,
>                          int flag, int marker_size)
>  {
>        /* Use union favor */
> -       flag = (flag & 1) | (XDL_MERGE_FAVOR_UNION << 1);
> +       flag = (flag & LL_OPT_VIRTUAL_ANCESTOR) |
> +              create_ll_flag(XDL_MERGE_FAVOR_UNION);
>        return ll_xdl_merge(drv_unused, result, path_unused,
>                            orig, NULL, src1, NULL, src2, NULL,
>                            flag, marker_size);
> @@ -342,7 +343,7 @@ int ll_merge(mmbuffer_t *result_buf,
>        const char *ll_driver_name = NULL;
>        int marker_size = DEFAULT_CONFLICT_MARKER_SIZE;
>        const struct ll_merge_driver *driver;
> -       int virtual_ancestor = flag & 01;
> +       int virtual_ancestor = flag & LL_OPT_VIRTUAL_ANCESTOR;
>
>        if (merge_renormalize) {
>                normalize_file(ancestor, path);
> diff --git a/ll-merge.h b/ll-merge.h
> index 57754cc..5990271 100644
> --- a/ll-merge.h
> +++ b/ll-merge.h
> @@ -5,6 +5,20 @@
>  #ifndef LL_MERGE_H
>  #define LL_MERGE_H
>
> +#define LL_OPT_VIRTUAL_ANCESTOR        (1 << 0)
> +#define LL_OPT_FAVOR_MASK      ((1 << 1) | (1 << 2))
> +#define LL_OPT_FAVOR_SHIFT 1
> +
> +static inline int ll_opt_favor(int flag)
> +{
> +       return (flag & LL_OPT_FAVOR_MASK) >> LL_OPT_FAVOR_SHIFT;
> +}
> +
> +static inline int create_ll_flag(int favor)
> +{
> +       return ((favor << LL_OPT_FAVOR_SHIFT) & LL_OPT_FAVOR_MASK);
> +}
> +

These two function names do not suggests that these are symmetric. How about get_ll_flavor() and create_ll_flavor()? Or flavor_to_ll_flag() and ll_flag_to_flavor().

Regards, Bert

Show 21 quoted lines
>  int ll_merge(mmbuffer_t *result_buf,
>             const char *path,
>             mmfile_t *ancestor, const char *ancestor_label,
> diff --git a/merge-recursive.c b/merge-recursive.c
> index 8a49844..c0c9f0c 100644
> --- a/merge-recursive.c
> +++ b/merge-recursive.c
> @@ -647,7 +647,8 @@ static int merge_3way(struct merge_options *o,
>
>        merge_status = ll_merge(result_buf, a->path, &orig, base_name,
>                                &src1, name1, &src2, name2,
> -                               (!!o->call_depth) | (favor << 1));
> +                               ((o->call_depth ? LL_OPT_VIRTUAL_ANCESTOR : 0) |
> +                                create_ll_flag(favor)));
>
>        free(name1);
>        free(name2);
> --
> 1.7.2.1.544.ga752d.dirty
>
>
Previous: Jonathan NiederNext: Jonathan Nieder
Message 24 of 35 in “Merge renormalization, config renamed”
  1. 0/3 Merge renormalization, config renamedEyvind Bernhardsen, Jul 2, 2010
  2. 1/3 Avoid conflicts when merging branches with mixed normalizationEyvind Bernhardsen, Jul 2, 2010
  3. 2/3 Try normalizing files to avoid delete/modify conflicts when mergingEyvind Bernhardsen, Jul 2, 2010
  4. 3/3 Don't expand CRLFs when normalizing text during mergeEyvind Bernhardsen, Jul 2, 2010
  5. Junio C HamanoJul 2, 2010
  6. 0/6 merge -XrenormalizeJonathan Nieder, Aug 4, 2010
  7. 1/6 merge-trees: push choice to renormalize away from low levelJonathan Nieder, Aug 4, 2010
  8. 2/6 merge-trees: let caller decide whether to renormalizeJonathan Nieder, Aug 4, 2010
  9. 3/6 ll-merge: let caller decide whether to renormalizeJonathan Nieder, Aug 4, 2010
  10. Junio C HamanoAug 4, 2010
  11. 4/6 rerere: migrate to parse-options APIJonathan Nieder, Aug 4, 2010
  12. 5/6 rerere: let caller decide whether to renormalizeJonathan Nieder, Aug 4, 2010
  13. Junio C HamanoAug 4, 2010
  14. 0/12 Re: rerere: let caller decide whether to renormalizeJonathan Nieder, Aug 5, 2010
  15. 01/12 t6038 (merge.renormalize): style nitpicksJonathan Nieder, Aug 5, 2010
  16. Ævar Arnfjörð BjarmasonAug 5, 2010
  17. Jonathan NiederAug 5, 2010
  18. 02/12 t6038 (merge.renormalize): try checkout -m and cherry-pickJonathan Nieder, Aug 5, 2010
  19. 03/12 t6038 (merge.renormalize): check that it can be turned offJonathan Nieder, Aug 5, 2010
  20. 04/12 merge-trees: push choice to renormalize away from low levelJonathan Nieder, Aug 5, 2010
  21. 05/12 merge-trees: let caller decide whether to renormalizeJonathan Nieder, Aug 5, 2010
  22. 06/12 Documentation/technical: document ll_mergeJonathan Nieder, Aug 5, 2010
  23. 07/12 ll-merge: make flag easier to populateJonathan Nieder, Aug 5, 2010
  24. Bert WesargAug 5, 2010
  25. Jonathan NiederAug 5, 2010
  26. Bert WesargAug 5, 2010
  27. Jonathan NiederAug 5, 2010
  28. 08/12 ll-merge: let caller decide whether to renormalizeJonathan Nieder, Aug 5, 2010
  29. 09/12 t4200 (rerere): modernize styleJonathan Nieder, Aug 5, 2010
  30. 10/12 rerere: migrate to parse-options APIJonathan Nieder, Aug 5, 2010
  31. 11/12 rerere: never renormalizeJonathan Nieder, Aug 5, 2010
  32. 12/12 merge-recursive --renormalizeJonathan Nieder, Aug 5, 2010
  33. Eyvind BernhardsenAug 5, 2010
  34. 6/6 merge-recursive: add -Xrenormalize optionJonathan Nieder, Aug 4, 2010
  35. Junio C HamanoAug 4, 2010

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.