git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Elijah Newren <newren@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Sep 2021, #03; Fri, 10)
Date: Sat, 11 Sep 2021 10:27:45 -0700	[thread overview]
Message-ID: <CABPp-BGR3dfJE7TZ+jkjDdWyeXYowmJhtoFaQ8_Abn=ZROhB5Q@mail.gmail.com> (raw)
In-Reply-To: <xmqqsfycqdxi.fsf@gitster.g>

On Fri, Sep 10, 2021 at 3:12 PM Junio C Hamano <gitster@pobox.com> wrote:
>
> --------------------------------------------------
> [New Topics]
>
> * en/stash-df-fix (2021-09-08) 3 commits
>  - stash: restore untracked files AFTER restoring tracked files
>  - stash: avoid feeding directories to update-index
>  - t3903: document a pair of directory/file bugs
>
>  Fix "git stash" corner case where the tentative change involves
>  changing a directory to a file (or vice versa).

I've got a v2 out to address all the feedback from Dscho, Stolee, and
you (https://lore.kernel.org/git/pull.1087.v2.git.git.1631269876.gitgitgadget@gmail.com/)

Relatedly, I also have a v2 of am-issues that hasn't been picked up
yet: https://lore.kernel.org/git/pull.1087.v2.git.git.1631269876.gitgitgadget@gmail.com/.
v1 was acked by Dscho; v2 has some fixes related to your feedback.

> * en/zdiff3 (2021-06-15) 2 commits
>  - update documentation for new zdiff3 conflictStyle
>  - xdiff: implement a zealous diff3, or "zdiff3"
>
>  "Zealous diff3" style of merge conflict presentation has been added.
>
>  Expecting a reroll.
>  cf. <CABPp-BE7-E03+x38EK-=AE5mwwdST+d50hiiud2eY2Nsf3rM5g@mail.gmail.com>

I just sent a reroll, since I did have some fixes from Phillip and
some new testcases, but it fails one of the testcases I made and I saw
another suboptimal case that I lost but would like to include.  I
still have this labelled RFC and it's definitely not ready.

I do plan to get back to it eventually, but am focusing more on other
topics, so you may want to eject this from seen for now.

> * ms/customizable-ident-expansion (2021-09-01) 1 commit
>  - keyword expansion: make "$Id$" string configurable
>
>  Instead of "$Id$", user-specified string (like $FreeBSD$) can be
>  used as an in-blob placeholder for keyword expansion.

Kinda disappointing to see mis-designs from CVS not only persist but
get extended.  Perhaps I'm just biased...

> * js/retire-preserve-merges (2021-09-07) 11 commits
>   (merged to 'next' on 2021-09-10 at f645ffd7a3)
>  + sequencer: restrict scope of a formerly public function
>  + rebase: remove a no-longer-used function
>  + rebase: stop mentioning the -p option in comments
>  + rebase: remove obsolete code comment
>  + rebase: drop the internal `rebase--interactive` command
>  + git-svn: drop support for `--preserve-merges`
>  + rebase: drop support for `--preserve-merges`
>  + pull: remove support for `--rebase=preserve`
>  + tests: stop testing `git rebase --preserve-merges`
>  + remote: warn about unhandled branch.<name>.rebase values
>  + t5520: do not use `pull.rebase=preserve`
>
>  The "--preserve-merges" option of "git rebase" has been removed.
>
>  Will merge to 'master'.

I'm not objecting, but I'm kind of surprised to see this after your
and Dscho's previous discussion at
https://lore.kernel.org/git/xmqqv939uis8.fsf@gitster.g/; I thought
it'd stay in next for a while.  Was this a mistake?

> * en/remerge-diff (2021-08-31) 7 commits
>  - doc/diff-options: explain the new --remerge-diff option
>  - show, log: provide a --remerge-diff capability
>  - tmp-objdir: new API for creating and removing primary object dirs
>  - merge-ort: capture and print ll-merge warnings in our preferred fashion
>  - ll-merge: add API for capturing warnings in a strbuf instead of stderr
>  - merge-ort: add ability to record conflict messages in a file
>  - merge-ort: mark a few more conflict messages as omittable
>
>  A new presentation for two-parent merge "--remerge-diff" can be
>  used to show the difference between mechanical (and possibly
>  conflicted) merge results and the recorded resolution.
>
>  What's the status of this one?

Well...you asked lots of good high level questions that I think you
felt I answered adequately.  I think that suggests the high level
ideas are at least okay.  It's also been tested in the wild for months
(and with the additional change of making `log -p` imply
--remerge-diff), so that suggests it won't blow up.

But as for actual patch review, the only one who has taken a look is
Sergey, who reviewed the diff-merges portion of patch 6 and was happy
with it.

It'd be great to get some more of these patches reviewed.  In
particular, if someone had time for just one patch, I'd really like to
see someone review one of these:
  * the tmp-objdir.c changes (patch 5)
  * the integration of all the pieces in log-tree.c and revision.c (patch 6)
  * the ll-merge.c changes (patch 3)

  reply	other threads:[~2021-09-11 17:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-10 22:11 What's cooking in git.git (Sep 2021, #03; Fri, 10) Junio C Hamano
2021-09-11 17:27 ` Elijah Newren [this message]
2021-09-11 17:42   ` Ævar Arnfjörð Bjarmason
2021-09-11 21:38     ` Junio C Hamano
2021-09-13 12:11   ` js/retire-preserve-merges, was " Johannes Schindelin
2021-09-12  1:57 ` Taylor Blau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CABPp-BGR3dfJE7TZ+jkjDdWyeXYowmJhtoFaQ8_Abn=ZROhB5Q@mail.gmail.com' \
    --to=newren@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).