From: Junio C Hamano <gitster@pobox.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Aug 2017, #04; Fri, 18)
Date: Tue, 22 Aug 2017 08:58:16 -0700 [thread overview]
Message-ID: <xmqqa82r4msn.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CACsJy8AM+dr_in_hW3y6APUo-cKsg+3sAZg9-7+02ZspSZcf=g@mail.gmail.com> (Duy Nguyen's message of "Tue, 22 Aug 2017 15:49:12 +0700")
Duy Nguyen <pclouds@gmail.com> writes:
> On Sat, Aug 19, 2017 at 4:26 AM, Junio C Hamano <gitster@pobox.com> wrote:
>> [Discarded]
>>
>> * nd/prune-in-worktree (2017-04-24) 12 commits
>> . rev-list: expose and document --single-worktree
>> . revision.c: --reflog add HEAD reflog from all worktrees
>> . files-backend: make reflog iterator go through per-worktree reflog
>> . revision.c: --all adds HEAD from all worktrees
>> . refs: remove dead for_each_*_submodule()
>> . revision.c: use refs_for_each*() instead of for_each_*_submodule()
>> . refs: add refs_head_ref()
>> . refs: move submodule slash stripping code to get_submodule_ref_store
>> . refs.c: refactor get_submodule_ref_store(), share common free block
>> . revision.c: --indexed-objects add objects from all worktrees
>> . revision.c: refactor add_index_objects_to_pending()
>> . revision.h: new flag in struct rev_info wrt. worktree-related refs
>>
>> "git gc" and friends when multiple worktrees are used off of a
>> single repository did not consider the index and per-worktree refs
>> of other worktrees as the root for reachability traversal, making
>> objects that are in use only in other worktrees to be subject to
>> garbage collection.
>
> I'm back and will try to continue this. Is it discarded because of
> lack of progress, or because the problem is already fixed some other
> way? A quick "git log --oneline" on important files has not revealed
> anything.
Welcome back.
I ejected it out of 'pu' due to inactivity and possibly because I
saw some conflicts with topics that were making progress back then.
I do not offhand know if the old one still merges cleanly to 'pu',
but it certainly wasn't because the topic was deemed unnecessary.
Thanks.
prev parent reply other threads:[~2017-08-22 15:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 21:26 What's cooking in git.git (Aug 2017, #04; Fri, 18) Junio C Hamano
2017-08-19 11:26 ` Torsten Bögershausen
2017-08-19 16:32 ` Junio C Hamano
2017-08-20 9:29 ` Jeff King
2017-08-20 9:40 ` Jeff King
2017-08-20 9:46 ` [PATCH] doc: fix typo in sendemail.identity Jeff King
2017-08-20 10:46 ` What's cooking in git.git (Aug 2017, #04; Fri, 18) Martin Ågren
2017-08-20 17:04 ` Junio C Hamano
2017-08-22 8:49 ` Duy Nguyen
2017-08-22 15:58 ` Junio C Hamano [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=xmqqa82r4msn.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.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).