On Fri, Jun 26, 2009 at 10:15 AM, Francisco J.
Ballesteros<[email protected]> wrote:
>
>>
>> Agreed. But you should realise that so far, you have only
>> been talking about a read-only usage of Git history. The
>> interesting part is to devise a way of adding to it. I don't
>> think I know good FS metaphors for all the things I need
>> there.
>>
>
> Why don't just let the user write to the tree?
At the moment, I simply don't see how well would that
fit into the use cases that I personally have around Git.
> If you write to a version that is a leaf it could add to that
> branch. If you write to a version that is not a leaf it could
> create a branch.
That is not a problem with Git. You can have sprouts from
every point in the history. Branches are only "tags" they
have no special meaning.
> When you want to make something that
> is not the default you could perhaps do by renaming the
> root dir (naming the version?) so that the new name describes the new version.
Ok, let me describe what issues I see: the 99% Git use case
on a UNIX system is the following:
$ git checkout <sha-1>
# [edit, compile, debug]*
$ [git status, git diff]*
$ git add file1 file2 file3
$ git commit -m"Change #1"
$ git add file4 file5
$ git commit -m"Change #2"
What can we offer with git-fs? Lets see...
% gitfs /remote-repo /mnt
% cd /mnt/trees/<sha-1>
So far so good, but once we start editing and
(especially!) compiling it seems unreasonable
for gitfs to be a backing store for *.o files
and other junk that has no place in the repo.
But suppose we even bite the bullet and
have all the junk managed by gitfs. What's
the FS action to correspond to:
$ git add file1 file2 file3
$ git commit -m"Change #1"
?
Does my tree get switched after the commint?
(remember I'm still in /mnt/trees/<sha-1>,
while commit has advanced everything to
/mnt/trees/<sha-2>).
Thanks,
Roman.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
