From: Sverre Rabbelier <srabbelier@gmail.com>
To: Chad Dombrova <chadrik@gmail.com>
Cc: "Tim 'Mithro' Ansell" <tansell@google.com>, git@vger.kernel.org
Subject: Re: read-only working copies using links
Date: Sat, 24 Jan 2009 19:43:20 +0100 [thread overview]
Message-ID: <bd6139dc0901241043h7087316bgcbcb5d9085d603ef@mail.gmail.com> (raw)
In-Reply-To: <AE9781AD-0B63-4AEE-9B62-20F9720B5DC4@gmail.com>
On Sat, Jan 24, 2009 at 19:39, Chad Dombrova <chadrik@gmail.com> wrote:
> what's the case against it, other than the obvious, that it will take more
> work?
Good question, I think it was mostly that, someone has to implement it
(possibly as part of packv4). Backwards compatibility is of course
always an concern, but I'm not too familiar with the subject, perhaps
other people on the list (or even those were at the gittogether) can
comment?
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2009-01-24 18:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-24 9:17 read-only working copies using links Chad Dombrova
2009-01-24 11:02 ` Sverre Rabbelier
2009-01-24 18:39 ` Chad Dombrova
2009-01-24 18:43 ` Sverre Rabbelier [this message]
2009-01-24 19:35 ` Jeff King
2009-01-24 19:34 ` Jeff King
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=bd6139dc0901241043h7087316bgcbcb5d9085d603ef@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=chadrik@gmail.com \
--cc=git@vger.kernel.org \
--cc=tansell@google.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).