Take a look at this thread:

 

http://groups.google.com/group/castle-project-devel/browse_thread/thread/be9
54df33f9b3bc6/a065c66637ee102f?lnk=gst
<http://groups.google.com/group/castle-project-devel/browse_thread/thread/be
954df33f9b3bc6/a065c66637ee102f?lnk=gst&q=notes#a065c66637ee102f>
&q=notes#a065c66637ee102f

 

Basically, we’re using svn:externals to push the
/Facilities/NHibernateIntegration/trunk/src folder back into the
/trunk/Facilities/NHibernateIntegration location, so the old build process
should “just work”. However, msbuild and vs.net won’t build properly,
because they will/should be pointing to the new
/Facilities/NHibernateIntegration/trunk/lib folder for binary dependencies,
and the /buildscripts (which is added to
/Facilities/NHibernateIntegration/trunk via svn:externals) folder for the
Castle.snk file).

 

-          rb

 

From: [email protected]
[mailto:[email protected]] On Behalf Of Tuna Toksoz
Sent: Wednesday, October 21, 2009 8:23 AM
To: [email protected]
Subject: Re: Git migration - step 1

 

The CI still uses the old convention, am i right? NH Facility doesn't have a
configuration so it is part of the "Castle" configuration, which i believe
includes all stuff.

 

What to do now?

Tuna Toksöz
Eternal sunshine of the open source mind.

http://devlicio.us/blogs/tuna_toksoz
http://tunatoksoz.com
http://twitter.com/tehlike





On Wed, Oct 21, 2009 at 6:00 PM, Tuna Toksoz <[email protected]> wrote:

Holy crap! How do we keep trunk in sync with this one? i mean

/trunk/Facilities/NHIntegration with /Facilities/NHIntegration/trunk?
Merges?



Tuna Toksöz
Eternal sunshine of the open source mind.

http://devlicio.us/blogs/tuna_toksoz
http://tunatoksoz.com

http://twitter.com/tehlike







On Wed, Oct 21, 2009 at 5:55 PM, G. Richard Bellamy <[email protected]>
wrote:


And make sure you check out from /Facilities/NHibernateIntegration/trunk to
do your work.


-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Mauricio
Scheffer
Sent: Wednesday, October 21, 2009 5:30 AM
To: Castle Project Development List
Subject: Re: Git migration - step 1



Not yet. Keep committing to SVN for now...

On Oct 21, 8:36 am, Tuna Toksoz <[email protected]> wrote:
> I am hoping to do some work on NH Facility and i am not in sync with the
> news. Can I do my work on git repository?
>
> Thank you.
>
> Tuna Toksöz
> Eternal sunshine of the open source mind.
>
>
http://devlicio.us/blogs/tuna_toksozhttp://tunatoksoz.comhttp://twitter.com/
<http://devlicio.us/blogs/tuna_toksozhttp:/tunatoksoz.comhttp:/twitter.com/>

tehlike
>
> On Wed, Oct 14, 2009 at 7:43 AM, Mauricio Scheffer <
>
>
>
> [email protected]> wrote:
>
> > Today I pushed the git migration of trunk with committer mappings and
> > all branches and tags:http://github.com/mausch/castle
> > Most of the committers already have github accounts, those who don't
> > please create one: Krzysztof, hammett, Markus and maybe others.
> > You'll notice that there are lots of tags like "attic/
> > IoC_ScopeBranch". Those are old branches that were merged to trunk but
> > git-svn somehow didn't get the merge. Having lots of unused branches
> > is very annoying in git so I archived them as tags as recommended in
> >http://stackoverflow.com/questions/1307114.
>
> > This is the repository that will be used as a base for each sub-
> > project repository, so now is the best time to make changes or resolve
> > any doubts.
>
> > We also need to discuss what workflow and branch structure we will
> > use... I like this one
> >http://wwwhome.cs.utwente.nl/~michaelw/projects/git-setup.html#sec9
> > but it might be overkill for Castle.
>
> > Cheers,
> > Mauricio





 

 




--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Castle Project Development List" 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/castle-project-devel?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to