2009/6/25 Devon H. O'Dell <[email protected]>:
>
> 2009/6/25 Manzur <[email protected]>:
>>
>> On 24 июн, 00:26, "Federico G. Benavento" <[email protected]> wrote:
>>> I have a particular question, in the end are you going to be able to use
>>> rm, cp, etc?
>>>
>>> why not just "touch file" instead "echo add" ?
>>>
>>
>> For what purpose do you want to use cp and rm?
>
> I think the idea is, `why can't I just cp /foo/bar /mnt/git' and have
> that function as `git/add bar'; rm as git/remove or whatever. The idea
> of having it in a fileserver is novel only when you are able to
> interact with the fileserver using standard utilities. I think we're
> not understanding what git/add is supposed to do that a cp wouldn't
> accomplish.
>
A potential point of confusion is repository actions versus sandbox
actions. GIT (and other source control systems) force explicit
actions to add and remove stuff to the repository from the sandbox so
that transient files (like object files or editor temporary files)
don't flow into the repo.
Conceptually, dynamic binding and private namespaces could be used to
address these, but how to do this isn't completely clear (to me). You
could explicitly mark the "source" files with chmod (or by default
mark all files in the sandbox as temporary, and explictly chmod out
the temporary flag via an explicit command or script). Another option
would be to have a copy-on-change synthetic file system sandbox bound
over the gitfs, but then you'll need to explicitly identify which
files you changed which are source files.
In my mind, figuring out how to do this naturally is the true crux of
this project and probably should have been worked out during the
proposal phase. That being said, the current approach being taken by
the student should suffice as a low-level file system, with a follow
up project being the implementation of a higher-level abstraction
(which is in part defined by the development workflow) which actually
gives the natural file system semantics most of the reponders
(including myself) seem to desire.
-eric
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Plan
9 Google Summer of Code" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/plan9-gsoc?hl=en
-~----------~----~----~----~------~----~------~--~---
