From: Liu Yubao <yubao.liu@gmail.com>
To: git@vger.kernel.org
Cc: Nguyen Thai Ngoc Duy <pclouds@gmail.com>, Sean <seanlkml@sympatico.ca>
Subject: Re: [RFC] separate .git from working directory
Date: Thu, 12 Oct 2006 13:04:19 +0800 [thread overview]
Message-ID: <452DCCD3.2080600@gmail.com> (raw)
In-Reply-To: <452DBF9E.7010900@gmail.com>
Liu Yubao wrote:
> Maybe the svk way is worth considering, it maintains a map relation
> between paths in repository and file system like this:
>
> $ svk checkout --list
> depot path path
> ==================================================================
> //path/in/repos/hello/world.c /path/in/fs/hello/world.c
Sorry, I made a mistake, svk maintains a map of the top directory
of checkout, not each file:
depot path path
====================================================================
//path/in/repos/myproject /path/to/myproject
>
> The problem is users must maintain this map when move or delete
> /path/in/fs/hello/world.c, it's a bit annoying.
>
> see
> http://svkbook.elixus.org/nightly/en/svk-book.html#svk.ref.svk.c.checkout
> for more information.
>
next prev parent reply other threads:[~2006-10-12 5:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 13:23 [RFC] separate .git from working directory Nguyen Thai Ngoc Duy
2006-10-11 14:41 ` Alex Riesen
[not found] ` <20061011184844.40b1205d.seanlkml@sympatico.ca>
2006-10-11 22:48 ` Sean
[not found] ` <20061011114303.0a23496e.seanlkml@sympatico.ca>
2006-10-11 15:43 ` Sean
2006-10-11 21:55 ` Nguyen Thai Ngoc Duy
2006-10-12 4:07 ` Liu Yubao
2006-10-12 5:04 ` Liu Yubao [this message]
2006-10-11 18:14 ` Martin Waitz
2006-10-11 21:46 ` Nguyen Thai Ngoc Duy
2006-10-11 22:22 ` Junio C Hamano
2006-10-12 5:21 ` Martin Waitz
2006-10-21 17:08 ` Nguyen Thai Ngoc Duy
-- strict thread matches above, loose matches on Subject: below --
2006-10-12 12:15 Sergio Callegari
2006-10-12 13:03 ` Alex Riesen
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=452DCCD3.2080600@gmail.com \
--to=yubao.liu@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=seanlkml@sympatico.ca \
/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).