From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Berlin To: DJ Delorie Cc: dan@cgsoftware.com, gdb@sources.redhat.com Subject: Re: Can anyone import trivial changes to libiberty? Date: Thu, 26 Jul 2001 14:55:00 -0000 Message-id: <87puanxsnm.fsf@cgsoftware.com> References: <20010726015013.A25620@nevyn.them.org> <87g0bjrhej.fsf@cgsoftware.com> <200107262134.RAA02989@greed.delorie.com> X-SW-Source: 2001-07/msg00388.html DJ Delorie writes: > Actually, this all changed when I took over libiberty. My machine has > a cron job that runs hourly and looks for needed merges, and writes a > script that does all the work for me. I just review the script and > run it when I get the email. The libiberties have been in 100% sync > since I started doing this. Coolness. > > Specific comments follow. > >> You are *supposed* to commit to both at once. > > You are *allowed* to. You should if you can. If you don't, or do it > wrong, the automerge picks up the difference. > > *Anyone* may merge any patch from gcc to other libiberty repositories > if they can't wait for the automerge, even if it's not their patch. > However, *nobody* can commit to non-gcc libiberties until after it's > committed to gcc (otherwise my scripts get confused, and it's a bad > idea anyway). Right. This much i knew. > >> In practice, sometimes people forget. > > Or can't check in to other repositories. Forgot about that. > >> Merges don't occur all that often. They usually occur when someone >> notices something they needed in one but not the other, and that >> they've gotten out of sync. > > They happen hourly now. Or, it checks hourly, and I commit it next > time I sit down at the computer ;-) > >> At least, this is my experience. > > Hopefully, we'll all have better experiences now. Good experiences are well, good. :) -- "I was reading the dictionary. I thought it was a poem about everything. "-Steven Wright