From: Emily Shaffer <emilyshaffer@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2021, #03; Tue, 9)
Date: Thu, 11 Nov 2021 14:40:00 -0800 [thread overview]
Message-ID: <YY2bwMQTtg/DY+39@google.com> (raw)
In-Reply-To: <YY2W6ESIxSz9lakK@google.com>
On Thu, Nov 11, 2021 at 02:19:20PM -0800, Emily Shaffer wrote:
>
> Once more, updates to submodule-UX-overhaul related work.
[...]
>
> Jonathan Tan: WIP v2 Conditional config includes remotes based on remote URL
> https://lore.kernel.org/git/cover.1635527389.git.jonathantanmy%40google.com
>
> Additional discussion ongoing, Jonathan is working on another reroll,
> with a substantially different implementation but same user-facing
> feature. I think this discussion can benefit from reviews with an open
> mind - this is another effort to solve "how can a team ship configs for
> anybody developing their project, in the least painful (to the user) way
> possible?" In other words, this is a spiritual successor to the
> "remote-suggested hooks" topic, in that we are still trying to solve the
> same problem.
Seems I slipped and missed a few others too.
Glen Choo: make create_branch accept any repository
https://lore.kernel.org/git/20211111171643.13805-1-chooglen@google.com/
More cleanup of implicit the_repository, this time in create_branch().
Glen Choo: RFC: Branches with --recurse-submodules
https://lore.kernel.org/git/kl6lv912uvjv.fsf%40chooglen-macbookpro.roam.corp.google.com
Some deeper discussion of branching strategy with regard to recursing
into submodules. This would be a really good one to follow and weigh in
on, because it is an unusual case where Git will need to be opinionated
about workflow in order to be useful, so we'd better be sure our opinion
is a good one.
- Emily
next prev parent reply other threads:[~2021-11-11 22:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 0:59 What's cooking in git.git (Nov 2021, #03; Tue, 9) Junio C Hamano
2021-11-10 12:47 ` js/scalar, was " Johannes Schindelin
2021-11-10 13:42 ` Ævar Arnfjörð Bjarmason
2021-11-11 18:25 ` Junio C Hamano
2021-11-12 9:32 ` Johannes Schindelin
2021-11-10 13:04 ` jc/fix-pull-ff-only-when-already-up-to-date, " Johannes Schindelin
2021-11-10 17:20 ` Junio C Hamano
2021-11-10 19:00 ` Alex Henrie
2021-11-10 19:09 ` Johannes Schindelin
2021-11-10 19:17 ` Junio C Hamano
2021-11-11 22:19 ` Emily Shaffer
2021-11-11 22:40 ` Emily Shaffer [this message]
2021-11-11 22:58 ` Junio C Hamano
2021-11-11 23:44 ` Glen Choo
2021-11-13 9:17 ` ab/config-based-hooks-2 etc. (was: What's cooking in git.git (Nov 2021, #03; Tue, 9)) Ævar Arnfjörð Bjarmason
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=YY2bwMQTtg/DY+39@google.com \
--to=emilyshaffer@google.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).