Hello,

* Scott Raynel <scottraynel <at> gmail.com> [2008-07-17 13:45]:
> Let's get -dfs merged ASAP. As Pavel points out it's been used for non- 
> DFS changes which makes it very hard to keep track of. My main concern  
> with the -dfs branch is that I don't really know what it gives us. Am  
> I right in the assumption that ad-hoc mode fixes went into -dfs?

Yes, at least 3662 comes to my mind, but also other changes related to
SWBA calculation.

> > I'd like to see changes in topic branches limited to their topics.
> > All other changes should be applied to the trunk first, so that they
> > are done in a synchronized manner.  Those changes could then be merged
> > to the topic branches.

ACK. I think the motivation behind the non-topic changes was to have a
branch where things can be tested before putting them into trunk. This
could be mitigated by using personal repositories and letting other
people fetch from them.

> > We could create a git mirror for those who wants personal branches,
> > but topic branches are not personal branches.
> Good idea - a read-only git-svn mirror that we can git-clone off for  
> personal local working branches would be great. Have the git-svn  
> mirror fetch changes from svn every hour or so. I already have a  
> similar set up locally and it works a treat.

I'm also using git-svn for madwifi, and I love it. However, I do not see
too much use in creating a read-only git clone of the repository,
besides of providing an option to accelerate the initial checkout and
encourage users/developers to get familiar with git (which is an
important point).

I am also not sure if it is possible to dcommit from such a cloned git
into the main svn.

I would like to see the main madwifi repo converted to git in a
reasonable time frame, but it requires several things to be done first.

If there is consensus about changing the repository, we should make a
list (on the wiki or as a task in trac?) of things which have to be
completed for such a heavy change:

 * merge -dfs back into trunk (will not be easier with git due to the
   already done untracked merges)

 * set up the read-only git clone (it probably could be auto-updated
   using a hook in svn)

 * make sure all madwifi developers with commit rights are familiar with
   git

 * deploy trac 0.11 and test if it cooperates well with git (might be
   tested on the read-only git clone of the current svn)

 * see if we can port the ticket history from trac-svn to trac-git.

Other contributions to this list are welcome.

Kind regards,

Georg
-- 
|| http://op-co.de ++  GCS/CM d? s: a-- C+++ UL+++ !P L+++ E--- W++  ++
|| gpg: 0x962FD2DE ||  N++ o? K- w---() O M V? PS+ PE-- Y+ PGP++ t*  ||
|| Ge0rG: euIRCnet ||  5 X+ R tv b+(+++) DI+(+++) D+ G e* h! r* !y+  ||
++ IRCnet OFTC OPN ||________________________________________________||

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
Madwifi-devel mailing list
Madwifi-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/madwifi-devel