From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: dangling commits in worktree
Date: Wed, 23 Nov 2016 15:15:03 +0100 [thread overview]
Message-ID: <20161123141502.GA10722@macbook.local> (raw)
In-Reply-To: <CACsJy8CPX3PDfhcaftDHy_U37rEACr7Q1gj_un4ALen45J9GZQ@mail.gmail.com>
On Wed, Nov 23, 2016 at 04:45:56PM +0700, Duy Nguyen wrote:
>
> It's a known issue that gc (and maybe some others that do rev-list
> --all, like fsck) "forgets" about some worktree's refs and you will
> see what you see.
Good. I just wanted to be sure it was a known problem.
Thanks for the info.
Luc
prev parent reply other threads:[~2016-11-23 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 0:52 dangling commits in worktree Van Oostenryck Luc
2016-11-23 9:45 ` Duy Nguyen
2016-11-23 14:15 ` Luc Van Oostenryck [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161123141502.GA10722@macbook.local \
--to=luc.vanoostenryck@gmail.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.
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).