To Roman:
I want to know yours and others' opinion about organizing files.
As I said above currently adding file1 to the repository is done by
(we're located in dir1/dir2 directory):
echo dir1/dir2/file1 > ../../ctl
This isn't good, especially without tab completion. The problem is
with the location of ctl file: user should specify either absolute or
relative path.
I've two solutions to that problem:
1) Create file server's special files in each subdirectory of the
<files> directory. So in the result we will have ctl, data in each
directory.
2) Make files under <files> directory read-only. Interpret data
written to the files under <files> dir as git commands. For example,
we could simply say
echo add > file1
to add file1 to the repository. The same could be done with other file-
specific git commands. Commands that aren't file-specific can be
executed via ctl and data files.
To Ron:
I agree with you that viewing branches would make git more convenient.
But decision was made towards saving on extra space needed for each
extracted branch.
But in my case it's possible to do it through extraction branch on the
fly.
I'll add that feature soon.
Thanks for your interest.
Manzur
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
