From: Duy Nguyen <pclouds@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Jun 2014, #04; Tue, 17)
Date: Thu, 19 Jun 2014 17:06:19 +0700 [thread overview]
Message-ID: <CACsJy8CXbbNEFigjibd-W3V3RaXOzsptMkufMybYCKPFAHM6UA@mail.gmail.com> (raw)
In-Reply-To: <xmqqfvj2jfkg.fsf@gitster.dls.corp.google.com>
On Thu, Jun 19, 2014 at 12:25 AM, Junio C Hamano <gitster@pobox.com> wrote:
> [Stalled]
> * nd/multiple-work-trees (2014-03-25) 28 commits
> - count-objects: report unused files in $GIT_DIR/repos/...
> - gc: support prune --repos
> - gc: style change -- no SP before closing bracket
> - prune: strategies for linked checkouts
> - checkout: detach if the branch is already checked out elsewhere
> - checkout: clean up half-prepared directories in --to mode
> - checkout: support checking out into a new working directory
> - use new wrapper write_file() for simple file writing
> - wrapper.c: wrapper to open a file, fprintf then close
> - setup.c: support multi-checkout repo setup
> - setup.c: detect $GIT_COMMON_DIR check_repository_format_gently()
> - setup.c: convert check_repository_format_gently to use strbuf
> - setup.c: detect $GIT_COMMON_DIR in is_git_directory()
> - setup.c: convert is_git_directory() to use strbuf
> - git-stash: avoid hardcoding $GIT_DIR/logs/....
> - *.sh: avoid hardcoding $GIT_DIR/hooks/...
> - git-sh-setup.sh: use rev-parse --git-path to get $GIT_DIR/objects
> - $GIT_COMMON_DIR: a new environment variable
> - commit: use SEQ_DIR instead of hardcoding "sequencer"
> - fast-import: use git_path() for accessing .git dir instead of get_git_dir()
> - reflog: avoid constructing .lock path with git_path
> - *.sh: respect $GIT_INDEX_FILE
> - git_path(): be aware of file relocation in $GIT_DIR
> - path.c: group git_path(), git_pathdup() and strbuf_git_path() together
> - path.c: rename vsnpath() to do_git_path()
> - git_snpath(): retire and replace with strbuf_git_path()
> - path.c: make get_pathname() call sites return const char *
> - path.c: make get_pathname() return strbuf instead of static buffer
>
> A replacement for contrib/workdir/git-new-workdir that does not
> rely on symbolic links and make sharing of objects and refs safer
> by making the borrowee and borrowers aware of each other.
Anything I can do to get this going again? The only thing I just found
(and have not fixed) is, I think $GIT_DIR/info/excludes and
$GIT_DIR/info/sparse-checkout should be per-worktree, not shared.
--
Duy
next prev parent reply other threads:[~2014-06-19 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 17:25 What's cooking in git.git (Jun 2014, #04; Tue, 17) Junio C Hamano
2014-06-19 10:06 ` Duy Nguyen [this message]
2014-06-19 20:40 ` Junio C Hamano
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=CACsJy8CXbbNEFigjibd-W3V3RaXOzsptMkufMybYCKPFAHM6UA@mail.gmail.com \
--to=pclouds@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).