From: Denton Liu <liu.denton@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2019, #02; Tue, 15)
Date: Tue, 15 Jan 2019 14:49:01 -0800 [thread overview]
Message-ID: <20190115224901.GA22644@archbookpro.localdomain> (raw)
In-Reply-To: <xmqq4la9r1sl.fsf@gitster-ct.c.googlers.com>
On Tue, Jan 15, 2019 at 02:31:06PM -0800, Junio C Hamano wrote:
> * dl/merge-cleanup-scissors-fix (2018-11-21) 2 commits
> - merge: add scissors line on merge conflict
> - t7600: clean up 'merge --squash c3 with c7' test
>
> The list of conflicted paths shown in the editor while concluding a
> conflicted merge was shown above the scissors line when the
> clean-up mode is set to "scissors", even though it was commented
> out just like the list of updated paths and other information to
> help the user explain the merge better.
>
> Ready?
The current patch should be kicked out in favour of the new revision,
v5 [1]. It hasn't been reviewed yet, though, so I expect some revisions
before it's finalised.
> * dl/remote-save-to-push (2018-12-11) 1 commit
> - remote: add --save-to-push option to git remote set-url
>
> "git remote set-url" learned a new option that moves existing value
> of the URL field to pushURL field of the remote before replacing
> the URL field with a new value.
>
> I am personally not yet quite convinced if this is worth pursuing.
After our discussion here[2], I resubmitted a new patch describing the
use-case of the feature. I was just wondering you're still "not quite
convinced" or if the description was just outdated.
Thanks!
-Denton
[1]: https://public-inbox.org/git/cover.1545745331.git.liu.denton@gmail.com/
[2]: https://public-inbox.org/git/xmqqtvjlisnu.fsf@gitster-ct.c.googlers.com/
next prev parent reply other threads:[~2019-01-15 22:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 22:31 What's cooking in git.git (Jan 2019, #02; Tue, 15) Junio C Hamano
2019-01-15 22:49 ` Denton Liu [this message]
2019-01-15 23:16 ` Junio C Hamano
2019-01-16 0:35 ` Duy Nguyen
2019-01-16 4:08 ` Junio C Hamano
2019-01-16 4:02 ` Eric Wong
2019-01-16 4:08 ` Junio C Hamano
2019-01-16 4:46 ` Junio C Hamano
2019-01-16 21:26 ` Thomas Gummerer
2019-01-17 18:35 ` Junio C Hamano
2019-01-18 9:58 ` ps/stash-in-c, was " Johannes Schindelin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190115224901.GA22644@archbookpro.localdomain \
--to=liu.denton@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.
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 NNTP newsgroup(s).