From: A Large Angry SCM <gitzilla@gmail.com>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Notes on supporting Git operations in/on partial Working Directories
Date: Sun, 17 Sep 2006 13:01:35 -0700 [thread overview]
Message-ID: <450DA99F.8000009@gmail.com> (raw)
In-Reply-To: <eek5l4$kaa$1@sea.gmane.org>
Jakub Narebski wrote:
> A Large Angry SCM wrote:
>
>> There is no fundamental reason Git can not support partial
>> checkouts/working directories. In fact, there is no fundamental reason
>> Git can not support operations on partial (sparse?) repositories in both
>> space (working content/state, etc.) and time (history); it's just a
>> matter of record keeping[*1*]. That isn't how the Linux kernel
>> developers want to use their VCS but it _is_ how others want to use
>> theirs.
>
> There is perhaps not much trouble with partial checkouts, but there is
> problem with partial _commits_, at least for snapshot based SCM (as opposed
> to patchset based SCM).
By "partial commit" I take it you mean a commit with only partial
information about the new (content) state? If so, the missing
information about the new state can be assumed to have not changed from
the previous recorded state (commit).
next prev parent reply other threads:[~2006-09-17 20:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 19:05 Notes on supporting Git operations in/on partial Working Directories A Large Angry SCM
2006-09-14 19:21 ` Shawn Pearce
2006-09-14 20:08 ` A Large Angry SCM
2006-09-14 19:50 ` Junio C Hamano
2006-09-14 20:19 ` A Large Angry SCM
2006-09-15 2:43 ` Junio C Hamano
2006-09-15 18:15 ` A Large Angry SCM
2006-09-17 10:43 ` Junio C Hamano
2006-09-17 18:47 ` A Large Angry SCM
2006-09-17 18:55 ` Jakub Narebski
2006-09-17 20:01 ` A Large Angry SCM [this message]
2006-09-17 20:28 ` Jakub Narebski
2006-09-17 21:11 ` A Large Angry SCM
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=450DA99F.8000009@gmail.com \
--to=gitzilla@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@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).