I'm by no means a git expert, or a commiter (instead one of those non-committing project leaders), but anyway... what if someone wants to branch per feature/change, then rebase to merge commits & push to their local master and then push to the origin (github)?
Would that not be possible? Would one be confined to either download multiple copies of history or not be able to utilize git in that fashion? What about stashing? Is it a worthwhile replacement using git in such a way and does it work with shallow clone? Mostly interested for my own understanding of git but I could also foresee myself using git in this fashion for castle projects as I do on other projects (not under github)... and I know nothing about shallow clones lol... Thanks, Rick Fleming On Mon, Feb 15, 2010 at 1:08 PM, Roelof Blom <[email protected]> wrote: > Yeah, I meant push *from* a shallow clone. And your right, it should work > now (it didn't really in git 1.5, don't know where I found that old release > notes...) > > Just followed your process for the auto tx facility, seems to be working > now! It's pushing to github ATM, takes a while... > > On Mon, Feb 15, 2010 at 4:54 PM, Mauricio Scheffer < > [email protected]> wrote: > >> The shallow clone is meant to be local. You won't push to your local >> repository, you'll push to the github repo. >> The problem would be if you couldn't push *from* a shallow repo, but >> IIRC you can. >> >> On Feb 15, 12:45 pm, Roelof Blom <[email protected]> wrote: >> > OK. >> > >> > IIRC you cannot push to shallow clones, so committers cannot use them, >> > >> > -- Roelof. >> > >> > On Mon, Feb 15, 2010 at 4:38 PM, Mauricio Scheffer < >> > >> > >> > >> > [email protected]> wrote: >> > > My point is: if you need the history, it will be there, and it will be >> > > usable/buildable. >> > > If you don't need the history, shallow clone. >> > > If we "partially" remove history, we will break older builds. >> > >> > > -- >> > > Mauricio >> > >> > > On Feb 15, 12:14 pm, Roelof Blom <[email protected]> wrote: >> > > > Perhaps (probably) it's my expectation that's wrong, I expected to >> see >> > > only >> > > > "relevant" commits. It's confusing to see MonoRail commits on the >> facilty >> > > > log. >> > >> > > > The fetching is very slow indeed, because it's fetching so much. The >> size >> > > on >> > > > disk of the AR facility is over 100MB. >> > >> > > > -- Roelof. >> > >> > > > On Mon, Feb 15, 2010 at 3:57 PM, Mauricio Scheffer < >> > >> > > > [email protected]> wrote: >> > > > > Yes, that was the point of this process: to have old history... >> other >> > > > > projects' history *could* be removed with further filter-branching >> but >> > > > > it's difficult and ultimately doesn't add any value. In 2004 or >> > > > > whenever the AR facility was started there was no independent AR >> > > > > facility project, it was all part of the same build. If someone >> needed >> > > > > to build RC2 he would need the whole thing anyway. If we just left >> the >> > > > > AR facility directory in the 2004 history it would be broken if >> you go >> > > > > back to that time. >> > >> > > > > If it bothers people to have to fetch all that history, use >> shallow >> > > > > clones. I implemented shallow clones in horn to minimize data >> > > > > transfer, and they can be used even for submodules to avoid >> history >> > > > > duplication in the superproject. >> > >> > > > > -- >> > > > > Mauricio >> > >> > > > > On Feb 15, 11:37 am, Roelof Blom <[email protected]> wrote: >> > > > > > Mauricio, >> > >> > > > > > There must have gone something wrong with the migration, the git >> log >> > > of >> > > > > the >> > > > > > AR facility shows each and every commit that was made since >> 2004... >> > >> > > > > > -- Roelof. >> > >> > > > > > On Thu, Feb 11, 2010 at 5:43 AM, Mauricio Scheffer < >> > >> > > > > > [email protected]> wrote: >> > > > > > > I just migrated the ARFacility: >> > >> > >http://github.com/castleproject/Castle.Facilities.ActiveRecordIntegra. >> > > > > .. >> > >> > > > > > > Here's a step by step guide of the process, complete with >> > > screenshots: >> > > > > > >http://docs.google.com/View?id=ddvpz7mf_202gzpzbjcx >> > >> > > > > > > Cheers, >> > > > > > > Mauricio >> > >> > > > > > > On Feb 2, 10:07 am, Mauricio Scheffer < >> [email protected]> >> > > > > > > wrote: >> > > > > > > > Roelof has tried my process with ARFacility and it turned >> out it >> > > > > isn't >> > > > > > > > very clear, I will run the process on another project, then >> copy >> > > & >> > > > > > > > paste here the exact commands I run plus maybe a couple of >> > > > > > > > screenshots. >> > >> > > > > > > > Cheers, >> > > > > > > > Mauricio >> > >> > > > > > > > On Feb 2, 3:54 am, Krzysztof Ko¼mic < >> [email protected]> >> > > > > > > > wrote: >> > >> > > > > > > > > Do we move officially to Git now with the projects that >> were >> > > > > released? >> > >> > > > > > > > > Krzysztof >> > >> > > > > > > -- >> > > > > > > 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]<castle-project-devel%[email protected]><castle-project-devel%2Bun >> [email protected]><castle-project-devel%2Bun >> > > [email protected]><castle-project-devel%2Bun >> > > > > [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]<castle-project-devel%[email protected]><castle-project-devel%2Bun >> [email protected]><castle-project-devel%2Bun >> > > [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]<castle-project-devel%[email protected]><castle-project-devel%2Bun >> [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]<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]<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.
