Tell me updates as you go, please.
Cheers, Henrik From: [email protected] [mailto:[email protected]] On Behalf Of Roelof Blom Sent: den 19 februari 2010 20:38 To: [email protected] Subject: Re: So do we GIT now? I am currently working on moving the AutoTX facility. 2010/2/19 Henry Conceição <[email protected]> Ok, so I'll continue to move some repos to github. I'm planning to move all the facilties on the next days. Is everybody ok with that? Cheers, Henry Conceição On Thu, Feb 18, 2010 at 6:21 PM, John Simons <[email protected]> wrote: > Agree > > On Feb 18, 5:19 am, Henry Conceição <[email protected]> wrote: >> So, we all agree that one scm is better than two and there is no >> problem to have all the history and not only the relevant part for >> each repo? >> >> Cheers, >> Henry Conceição >> >> On Tue, Feb 16, 2010 at 7:03 AM, Roelof Blom <[email protected]> wrote: >> > Inline >> >> > On Tue, Feb 16, 2010 at 9:24 AM, John Simons <[email protected]> >> > wrote: >> >> >> Mauricio, >> >> >> All very good points :) >> >> Inline >> >> >> Cheers >> >> John >> >> >> On Feb 16, 12:29 pm, Mauricio Scheffer <[email protected]> >> >> wrote: >> >> > * It's simpler to have one SCM than two. >> >> I agree, but I thought we were going to freeze svn and make it >> >> readonly, or is this not the plan? >> >> > Which thread was that decided on? I don't like the idea of having two SCM's, >> > see the recent thread on the users list about APTCA in which people checkout >> > from the "wrong" svn project. Another reason not to keep SVN is to bring >> > down bandwith costs for Stronghold. >> >> >> > * Browsing history is a big selling point of git, since you have all >> >> > history locally there is no network overhead. >> >> No problems with this except maybe as Roelof pointed out "I expected >> >> to see only "relevant" commits" to the current project. >> >> > As I also pointed out this was my expectation, which can be far off reality >> > :-) >> > I'm with Mauricio on this. If all that history is really annoying the hell >> > out of somebody he can always do some magic with git-filter-branch. >> >> > -- Roelof. >> >> > -- >> > 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] <mailto:castle-project-devel%[email protected]> . >> > For more options, visit this group at >> >http://groups.google.com/group/castle-project-devel?hl=en. > > -- > 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] <mailto:castle-project-devel%[email protected]> . > For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en. > > -- 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] <mailto:castle-project-devel%[email protected]> . For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en. -- 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. -- 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.
