Since there were no relevant replies, I'm going to use option 1 below. My reasoning: this is a development area. It'll take some time to get the code to compile and be even somewhat acceptable, in the meantime, I don't want to clatter the trunk.
When iser target will get to a working state, we'll move it to the trunk, possibly joining it with the iser (initiator) ulp. Dan On 4/10/06, Dan Bar Dov <[EMAIL PROTECTED]> wrote: > We are starting to work on open-source iser-target code. > I want to create a directory for it in the SVN. > There are several options I can think of: > > 1. https://openib.org/svn/gen2/ulps > An empty directory, I don't know what its for, but could containe the > iser-target > > 2. https://openib.org/svn/gen2/trunk/src/linux-kernel/infiniband/ulp > Together with the rest of the ulps, in the trunk > > 3. https://openib.org/svn/gen2/branches > create a new branch for it (branch of what?) > > 4. > https://openib.org/svn/gen2/branches/openib-candidate/src/linux-kernel/infiniband > I have no idea what is that for, but the path seems appropriate. > > I'm leaning towards option 1 myself. > > Dan > _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
