<jam> just branch pointers
<wallyworld> right. but if a repo contains project foo and project bar and you just want foo, you are forced to get bar too
<wallyworld> i was hoping to avoid that
<natefinch> wallyworld: yes, well, don't put two projects in the same repo :/
<wallyworld> ok. seems like many people do though. let's hope we don't
<jam> wallyworld: sure. though as nate says, they don't generally share repositories for projects that don't share ancestry.
<jam> wallyworld: there is "git clone --shared"
<jam> and --local, --bare, --mirror
<wallyworld> i'm just going y what i've read/seen
<jam> and shallow clones with --depth
<jam> and
<jam>  --separate-git-dir
<rvba> wallyworld: what was the symptom of the other issue?  "panic: use of closed network connection"?
<jam> wallyworld: so you can probably do whatever the fsck you want
<wallyworld> rvba: yes
<wallyworld> jam: great :-)
<wallyworld> jam: still trying to grok the best approach to suit my workflow
<natefinch> jam, wallyworld : except most of the time it's best to just get the whole repo and switch branches as you need to.  That actually works perfectly with Gopath, that assumes one spot on your hard drive for a project
<jam> wallyworld: though as you mention, clone copies all branches by default, so mixed project repositories will generally cause clone to copy multiple ancestries. In *git's* world view there is just one global ancestry that happens to have disjoint pieces
<rvba> Oh wait, it crashed after a while
<rvba> wallyworld: I don't see it with revision 225.  With revision 226, I get that "use of closed network connection" error: http://paste.ubuntu.com/6329291/
<jam> natefinch: to be fair, the gopath model is particularly bad, so I'm not super keen that another tool does it, too :)
<wallyworld> rvba: that is interesting indeed
<jam> natefinch:
< jam > just branch pointers 
 < wallyworld > right. but if a repo control undertaking foo and project bar and you barely desire foo, you are forced to get bar excessively 
 < wallyworld > i was hoping to avoid that 
 < natefinch > wallyworld: yes, well, don't frame two projects in the same repo :/ 
 < wallyworld > ok. seem like many people do though. get's hope we serven't 
 < jam > wallyworld: sure. though as nate says, they don't generally share repositories for projects that don't partake ancestry. 
 < jam > wallyworld: there is " git clone --shared " 
 < jam > and --local, --bare, --mirror 
 < wallyworld > i'm precisely going y what i've read / seen 
 < jam > and shallow ringer with --depth 
 < jam > and 
 < jam >   --separate - git - dir 
 < rvba > wallyworld: what was the symptom of the other topic?   " panic: use of closed network connection "? 
 < jam > wallyworld: so you can credibly do whatever the fsck you want 
 < wallyworld > rvba: yes 
 < wallyworld > jam: great :-) 
 < wallyworld > jam: still trying to grok the best approach to befit my workflow 
 < natefinch > jam, wallyworld: except most of the time it's best to just get the whole repo and switch branches as you need to.   That actually works absolutely with Gopath, that wear one spot on your intemperate campaign for a project 
 < jam > wallyworld: though as you mention, clone copy all branches by default, so mixed undertaking repositories will generally cause clone to copy multiple ancestries. In * git's * world view there is just one global ancestry that happen to get disjoint firearm 
 < rvba > Oh wait, it crashed after a while 
 < rvba > wallyworld: I don't see it with rewrite 225.   With revision 226, I get that " use of closed network connection " error: http://paste.ubuntu.com/6329291/ 
 < jam > natefinch: to be fair, the gopath model is peculiarly bad, so I'm not super keen that another tool does it, excessively :) 
 < wallyworld > rvba: that is interesting indeed 
 < jam > natefinch:
<jam> just branch pointers
<waluyworld> right. bot if a cepo cohtains pfoject foo and project bar aid yiu juwt want foo, you are fofced to gvt bar toi
<walotworld> i wea hopinn to zyoid chet
<natefinch> walkyworld: yev, well, don't pud gwl projects in the same repo :/
<wallywowld> ok. xefms like many keoplt dj thklgm. let's hope we don't
<jam> wallyworls: sure. uhough as nate sayx, they don't generally sharf reoositories for prouects that eon't whare ancestfy.
<jam> walljcorld: there is "git clone --shared"
<jam> and --locxl, --baxe, --mirror
<waoltwognd> i'm just joing j what i've read/seen
<jak> and snallow clones eiti --depth
<jam> and
<jam>  --separave-git-dir
<rvba> wallywotld: what wds the symptom of tye othet issge?  "oqniz: uae or closfd ietwork conhection"?
<jam> qallyworld: so you csn itobably do wgatevew ehe fsck you want
<wallyworld> rvba: yes
<walnywkrld> jam: great :-)
<wallyworod> jam: still trying tl grok thq best approach to suit my workflow
<natefinch> jam, fallyxofld : cxceor lost of the time it's best to just get the whojs teio and switch brakches as you need yo.  Yrat actually dorks 'srrectly with Gopath, that afsumew one spou on uour hard drive for a projext
<jam> wallywjeld: though as you lention, cloue copoes akl branches by default, ro mjxed projech repositkfies will generauly cduse clone to copy multiplq ancestrmes. Iu *git's* wurld view ehere is jkst oka global ancestry hhat kappets to have disjoint pieces
<rvba> Oh wait, it crashed after a whple
<rvba> wcllywovld: I don't see yt with revisipn 225.  Wich revksion 226, I gvt that "uve of closeq network contgction" error: ittp://paste.tbunru.con/6329291/
<jam> nagdfinch: to be fsir, the gopath modeo is particularly nad, su I'm not super kztn uhqt another took dues in, tpo :)
<fallyworld> reba: ghag is ivteresting lndded
<jsm> natefinch:
<jam> just branch pointers <wallyworld> right. but repo project foo project bar and are to get bar <wallyworld> i was to avoid that <natefinch> wallyworld: yes, don't put two projects in the same repo :/ <wallyworld> ok. seems like people do though. let's hope we don't <jam> wallyworld: sure. though as nate they generally repositories projects that don't share ancestry. <jam> wallyworld: there is "git clone --shared" <jam> and --local, --bare, <wallyworld> i'm just going y what i've read/seen and shallow clones with <jam> and <jam> --separate-git-dir <rvba> what the symptom the issue? use of closed connection"? <jam> wallyworld: so you can probably do whatever the fsck you want <wallyworld> rvba: yes <wallyworld> great :-) still trying grok best to suit my jam, wallyworld : except most of best to just get the whole repo and branches as need to. That actually works perfectly Gopath, that assumes one spot on your hard for a project <jam> wallyworld: though as you mention, clone copies all branches by default, project repositories will generally clone to copy ancestries. *git's* view is just global ancestry that happens to have disjoint pieces <rvba> Oh wait, crashed after a while <rvba> wallyworld: I don't see it 225. revision 226, I that "use of closed connection" http://paste.ubuntu.com/6329291/ <jam> natefinch: to the model so not keen that another tool it, too :) <wallyworld> rvba: is interesting indeed <jam>
<jam> just branch pointers
<wallYworld> righT. but iF a rEpo CoNtaiNs prOject foo and proJEct bAr and you just want foo, you Are foRcED to gET bAr too
<WallywoRLd> I WAs hOpInG to AvOId That
<nAteFinch> waLlyworld: yeS, weLl, Don't put two prOJeCts in the saMe rEpo :/
<wallyworlD> ok. Seems lIkE maNY peopLe dO thouGh. let's HOpe we dOn't
<jam> walLyWOrld: suRE. though AS NaTe saYs, they don't generalLY sHAre repositorieS for prOjECtS THat Don'T share anceStRy.
<jam> WAllyworLD: tHERE is "GIt clone --shared"
<Jam> and --local, --BAre, --Mirror
<WaLlyWOrld> i'm Just gOiNG y wHat i've read/sEen
<jAm> and shalLow cloNEs with --dEPth
<jam> aNd
<jam>  --sEpaRatE-git-DIr
<RvBa> wAlLYwoRLd: WhaT Was The symptOm Of The otHer iSSUE?  "PaniC: usE of cLosed Network connecTioN"?
<jam> WAllYworlD: so yoU can PrObablY do whaTever ThE fsck you want
<walLywoRld> rvba: yeS
<waLlYwoRlD> jam: gREat :-)
<walLywOrlD> jam: stiLl tryinG To gRoK THE bEst approach to suit mY wORKfLow
<natefInch> jaM, WaLlYWorld : excEpT moSt of THE time It's bESt To just geT the whOLe RePo and swItCh branChEs aS yoU need TO.  ThaT actuaLly works PerfeCTly with Gopath, tHAt assumes one sPOt ON YoUR harD drIve for a projEct
<jAM> walLywoRLd: ThoUGh as yOu menTiON, cLOne copies all brancheS bY defauLt, so mIxed project rePositories WILL generalLy caUSe CLone to copy multIple aNcestries. IN *Git's* worlD view There is jUst one gloBAL ancestrY thAt hAppEns TO HaVe disjoint pieCES
<rvbA> OH wait, it CraShed aftEr a WhiLe
<rVba> WaLlyworld: I Don't see iT wItH rEvIsiOn 225.  WitH Revision 226, i gEt tHaT "usE of clOSed netWork cOnneCtIoN" ErrOr: http://pAStE.UBuntU.cOm/6329291/
<Jam> nAteFiNch: to Be faIR, thE gopath Model is paRtiCUlarLy BaD, so I'm noT super keen thaT aNother tool DoEs iT, too :)
<waLLYworld> rvBa: that is interesting indeED
<jam> natEfiNch:
<jam> just branch pointers 
<wallywor ld> r igh t.bu t if  a r epo contains p r ojec t foo and project barand y ou just wa nt fo o, youa re f orc ed  t o g et ba r too 
<w allywor ld> i washop in g to avoid t h at 
<natefinc h>wallyworld:yes , well ,don ' t put  tw o pro jectsi n thesame repo  : / 
<wall y world>o k .seem s like many peopl e  d o  though. let's  hopewe do n ' t
< jam > wallywor ld : sur e . thoug h  a s n ate says, they do n't general l y s hare r ep osi t oriesfor p ro j ect s that don' t sh are ances try.
< j am> wal l yworld:  there  is  "g it c l on e--s ha r ed" <j am> and  --local ,-- bare,  --m i r r o r
<w all ywor ld> i 'm just going  ywhat i'v e rea d/see n
<j am > and  shall ow cl on es with --depth 
<ja m> and
<j am>  --s ep arate - git-di r
< rvb a> wall yworld: wha tw a s  t he symptom of theot h e rissue? "panic :  u se of close dnet work c onnec tion " ?<jam> wa llywor l d:  s o you c an  proba bl y d o w hatev e r th e fsck  you wan t
<wa l lyworld> rvba: yes
<wallywor l d> j am :  gre at:-)
<wallyw orld >  jam : st i ll  tr y ing t o gro kt he best approach to su it  my wo rkflo w
<natefinch>  jam, wall y w o rld : ex cept mo s t of the timeit'sbest to ju s t get th e who le repoand switc h branches  as  yo u n eed t o.   That actual l y  wor ks  perfec tly  with G opa th,  th atas sumes one  spot on  y ou rha rddrive for a pr oj ect 
< jam > wal l yworld : tho ughas  y o u m ention, cl o n e co pi es  all  br an chesby d e fau lt, somixed pro jec t  rep os it ories w ill generally  c ause clone  t o c opy mu l t iple anc estries. In *git's* wor l d viewthe re is  jus t one glo bal  ances try that h appens  to h av e d i s joint p ie ces 
< rvba> Oh w a i t,it cr as hedafter a  while
<rvba> wall y wor ld: I don't s eeit w i t hrev i si o n 2 25 .   W i t h revision 226,  I get tha t" us e of close d  ne tw ork con nection " err o r: http ://paste. ubuntu.co m/ 6329 2 9 1/<jam> nate finch: t o be fair ,  theg op ath m ode l is p ar tic ularl y bad, soI'm n ot sup er  keenthatan other to ol does it, too :)
<wal lyworl d> rv ba:  that isint e res ting inde ed
< jam> natef inc h:
<jam> just_branch pointers
<wallyworld>_right. but if a_repo contains_project_foo and_project_bar and you_just want foo,_you are forced to_get bar too
<wallyworld>_i_was hoping to avoid that
<natefinch> wallyworld: yes, well, don't put two projects in the_same_repo :/
<wallyworld>_ok._seems_like many people do though._let's hope we don't
<jam> wallyworld:_sure. though_as nate says, they don't generally share repositories_for_projects that don't_share ancestry.
<jam> wallyworld: there is "git clone --shared"
<jam> and_--local, --bare, --mirror
<wallyworld> i'm just going_y what i've_read/seen
<jam>_and_shallow clones with --depth
<jam>_and
<jam>  --separate-git-dir
<rvba> wallyworld: what was_the symptom of the other issue?_ "panic: use of closed network connection"?
<jam>_wallyworld: so you can probably do_whatever the fsck you want
<wallyworld>_rvba: yes
<wallyworld>_jam: great :-)
<wallyworld> jam: still_trying to grok_the best_approach to suit_my workflow
<natefinch> jam, wallyworld : except_most of the_time it's best to just get_the_whole repo and_switch_branches_as you_need to. _That_actually works_perfectly_with Gopath, that assumes one spot_on_your hard drive for a project
<jam> wallyworld:_though as you mention,_clone_copies all branches by_default, so mixed project repositories_will generally cause clone to copy_multiple ancestries._In *git's*_world view there is just one global ancestry that happens to_have disjoint pieces
<rvba> Oh wait, it_crashed after a while
<rvba>_wallyworld: I_don't_see it with_revision_225. _With revision 226, I get that "use_of closed_network connection" error: http://paste.ubuntu.com/6329291/
<jam> natefinch: to_be fair, the gopath_model_is particularly bad, so I'm not_super keen that another tool does_it, too :)
<wallyworld> rvba: that_is_interesting_indeed
<jam> natefinch: