From: Stefan Beller <sbeller@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Sep 2017, #04; Mon, 25)
Date: Mon, 25 Sep 2017 11:30:38 -0700 [thread overview]
Message-ID: <CAGZ79kaM+PGzFdGVkdLszAuz9kEatzf_ESC+KMjkRnwXS5FaVw@mail.gmail.com> (raw)
In-Reply-To: <xmqq7ewndyu1.fsf@gitster.mtv.corp.google.com>
>
> * sb/parse-options-blank-line-before-option-list (2017-08-25) 1 commit
> - usage_with_options: omit double new line on empty option list
>
> "git worktree" with no option and no subcommand showed too many
> blank lines in its help text, which has been reduced.
>
> Superseded by bc/rev-parse-parseopt-fix?
yes it is, please retract this one.
> * sb/submodule-recursive-checkout-detach-head (2017-07-28) 2 commits
> - Documentation/checkout: clarify submodule HEADs to be detached
> - recursive submodules: detach HEAD from new state
>
> "git checkout --recursive" may overwrite and rewind the history of
> the branch that happens to be checked out in submodule
> repositories, which might not be desirable. Detach the HEAD but
> still allow the recursive checkout to succeed in such a case.
>
> Undecided.
> This needs justification in a larger picture; it is unclear why
> this is better than rejecting recursive checkout, for example.
I'll revisit this with fresh eyes, the original plan was to get
jn/per-repo-obj-store done to have more fundamental operations
available to do the right thing, whatever it is, though.
>
> * jn/per-repo-obj-store (2017-09-07) 39 commits
We intend to get this one rolling again.
prev parent reply other threads:[~2017-09-25 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 7:25 What's cooking in git.git (Sep 2017, #04; Mon, 25) Junio C Hamano
2017-09-25 18:30 ` Stefan Beller [this message]
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=CAGZ79kaM+PGzFdGVkdLszAuz9kEatzf_ESC+KMjkRnwXS5FaVw@mail.gmail.com \
--to=sbeller@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).