Help regarding netfs callbacks

2008-06-01 Thread Madhusudan C.S
Hi all,
I am working on implementing GNU/Linux compatible procfs. I am
using netfs for translator implementing this translator as it was planned. I
have quite a few quiries regarding netfs programming and using its
callbacks. Someone who know about these please help me.

1. Some of the existing translators define two structures one with the
netnode and another generally with the name of the translator, say netnode
and procfs in this case as I have done now. Whats the essential difference
between two structures and what different information are they intended to
contain? (Additionally ftpfs also implements two structures for dir and
dir_entry. Is it necessary to maintain these structures, are there any
special advantages in doing so?)

2. I did not quite get the concept of  netfs_get_dirents callback which
netfs says is used for fetching the directories. What is it expected to do?
What do we have to define and do within this callback? Most of the existing
translators seem to implement the same code(I can say its a copy). Why is it
so? Can I take those things from there? But I dont want to copy paste
something without knowing what is actually happening. Can someone explain
please?


-- 
Thanks and regards,
Madhusudan.C.S

Blogs at: www.madhusudancs.info


Re: Revision control

2008-06-01 Thread Arne Babenhauserheide
Since there were no objections, I assume a bit of arguing about possible cvs 
replacements might be useful. 

Still, this doesn't imply that any decision is there to replace cvs, just that 
a discussion about alternatives might yield interesting results. 

Am Freitag 30 Mai 2008 20:10:04 schrieb Ivan Shmakov:
>   The total disk usage for the two repositories will typically be
>   less than the doubled disk usage for any one of them.  (As the

Mercurial offers the same, for GNU/Linux and Windows. 

>   Also, it's possible to use a related local repository as an
>   additional source for changesets while cloning a remote
>   repository over the network, allowing for the bandwidth saving
>   as well.

Did you test the efficiency (and how often it can be used)? 

>   Also, as Mercurial records only the parents of the revisions
>   (and not all their ancestors), it should become challenging to
>   implement the ``cherry-picking'' feature.  (Though I don't

There's a Google Summer of Code project doing that. 

And Mercurial knows the parents of parents, so it knows the whole history step 
by step. It avoids keeping duplicate data that way. 

>   really know any good implementation of it except for that in GNU
>   Arch.)
>
>   In general, I'd prefer Git as the DVCS for Hurd.  

I used it for the wiki, and it feels like walking in the underbrush of a dense 
forest. 
There's much value in it, but there are also many hidden holes in the ground 
and denser patches of underbrush which I can't cross without carving a path 
first. 

I prefer to avoid having to cut a path, when I can get avoid the hassle and 
get the same power by using Mercurial. 

As a plus, I like the Mercurial documentation very much. Even advanced stuff 
can be found quickly. 
-> Example: The free licensed Mercurial book: http://hgbook.red-bean.com/

And I like what I know about the development model of Mercurial: Discussing 
the possible implications of every change in depth before introducing it, so 
it doesn't surprise me with features that might wreak havoc my repositories. 

In short: Mercurial just works, and I like that. 

>   Alas, I'll 
>   hardly have any spare time to dedicate to the Hurd development
>   in any foreseeable feature.

I'll likely stick to working on the wiki, so the new repository format doesn't 
matter that much to my personal work, but I'd prefer to see the Hurd 
development more accessible, and even though there are many good candidates, 
Mercurial is best suited for that, at least in my opinion. 

Best wishes, 
Arne
-- 
Unpolitisch sein
Heißt politisch sein
Ohne es zu merken. 
- Arne Babenhauserheide ( http://draketo.de )

-- Weblog: http://blog.draketo.de
-- Infinite Hands: http://infinite-hands.draketo.de - singing a part of the 
history of free software. 
-- Ein Würfel System: http://1w6.org - einfach saubere (Rollenspiel-) Regeln

-- Mein öffentlicher Schlüssel (PGP/GnuPG): 
http://draketo.de/inhalt/ich/pubkey.txt


signature.asc
Description: This is a digitally signed message part.