Open Source Integrated Library System

Evergreen on IRC

#evergreen Logs for Saturday, May 14th, 2011

< Friday, May 13th, 2011Raw Log FileSunday, May 15th, 2011 >
#TimeNickMessage
#01:24:55pmpafk has quit IRC
#01:46:05pmpafk has joined #evergreen
#02:24:48pmpafk has quit IRC
#02:46:56pmpafk has joined #evergreen
#04:31:07pmpafk has quit IRC
#06:27:43natschil has joined #evergreen
#07:04:37natschil has quit IRC
#08:30:45eeevilbshum: re xpath, yes, the attrs should start with @. good catch
#08:31:38tsbereeeevil: My latest lazy circ look more like you think it should?
#08:31:52eeevilgmcharlt: when are you locking svn, sir?
#08:32:42eeeviltsbere: sorry, not nearly enough coffee yet ... you mean the barcode guessing prefix stuff?
#08:35:02tsbereeeevil: Yea. And last I heard he wants to have it done by 4? Beyond that he didn't provide details.
#08:35:42eeeviltsbere: yeah, I was going to try to shove in xpath cleanup, but I can just stage that
#08:36:17tsbereeeevil: bshum aslo said the @ind1 entries are already fixed in trunk?
#08:37:10eeeviltsbere: I know they were fixed in some places ... just looking into it now
#08:37:16eeevildbs did that, IIRC
#08:37:47eeevilyep: http://svn.open-ils.org/trac/ILS/changeset/19644 and friends
#08:38:39natschil has joined #evergreen
#08:39:02eeevilin 2.0.3+
#09:05:56eeeviltsbere: yes, that's looking great ... some minor nits (spurious data.list.au[0].ws_ou() in get_barcode, very sparse spacing) and one slightly less minor one -- in at least one place we were checking for an ils_event and distinguishing between different values (1002 /* ACTOR_USER_NOT_FOUND */ vs, well, anything else) ... there are permission checks in open-ils.actor.user.retrieve_id_by_barcode_or_username for 1) authenticatedness and 2) VIEW_USER perm, a
#09:06:09eeevil(that probably got truncated
#09:09:25natschil has quit IRC
#09:09:37eeeviltsbere: I'll comment on the LP bug
#09:09:41natschil has joined #evergreen
#09:26:03tsbereeeevil: My list of things to think about possibly doing included "check session and one or more perms". I think I even have notes on that around here somewhere......can get on that fairly quickly.
#09:26:39tsbereAnd I know where that spurious data.list.blah was from. Originally grabbed that to a variable, then stopped using it all over the place.
#09:27:28tsbere dislikes the sheer number of iterations that one function went through in trying to get it to work
#09:30:53natschil has quit IRC
#09:39:21gmcharlteeevil: will lock SVN at 2 p.m. today, then do the final push
#09:39:27gmcharltthen git-land for us all
#09:56:29eeevilgmcharlt: it should be as simple as adjusting the origin repo in my .git/config to point at that instead of the ESI clone, for the master branch, when complete. yes?
#09:56:43gmcharltrigh
#09:56:45gmcharltt
#10:34:47tsbere would like to make it known that some days he hates perl
#12:14:21Digital_Pioneer has joined #evergreen
#12:25:31tsbereeeevil: Pushed a new commit to the lazy_circ2 branch. Should I bother adding an updated patch to launchpad?
#12:36:13GrandGentil has joined #evergreen
#12:38:04GrandGentil has quit IRC
#12:38:43Digital_Pioneer has quit IRC
#12:58:44gmcharltclearing topic branches added yesterday to give us a pristine start
#13:05:02tsbereI would offer to assist with this, but it appears you have it well in hand for now
#13:07:16gmcharlttsbere: if you're looking for something to do, mind giving a hand setting up post-receive hooks to email evergreen and opensrf patches to open-ils-commits?
#13:08:00tsbereI can give that a shot, though that is one subject I have yet to touch on git (emailing on commit)
#13:08:16tsbereAlso, doesn't opensrf have a different list?
#13:08:28gmcharltyou're right, it does
#13:09:04gmcharlttsbere: preferred login name for shell accounts?
#13:09:17tsberetsbere works.
#13:18:24gmcharlttsbere: ok, you now have an account on the git server
#13:18:32gmcharltyour pub key should work
#13:20:58tsbereDo we want to rig up email in the easiest fashion for later repos, or per repo (which will require more work later)?
#13:22:34gmcharltlet's assume that people will want email as an option for all repos, even though only Evergreen.git and OpenSRF.git will need it right away
#13:28:10tsbereThus, install the email hook via gitolite so it ends up everywhere
#13:29:31gmcharltyep; since I believe there's per-repo settings to turn it on or off and set the destination, that sounds dandy
#13:29:55tsbereYep. I assume I have some form of sudo rights.
#13:30:01tsbere hasn't tried yet
#13:30:11gmcharltyou have sudo all
#13:36:33tsbereShould we clean up the other repos?
#13:36:46tsbere(the ones without the uppercase first letter)
#13:37:19gmcharltyeah, I'll do that now
#13:38:50tsbereShould I push the email settings now, or should I push to a new branch for merging when we are ready later?
#13:38:57tsbere(on the gitolite admin repo)
#13:39:47gmcharltgo ahead and do it now
#13:40:08gmcharltyou can make a temp repo for yourself to test in the meantime
#13:41:14tsbereI'll just throw a mailing list entry on testing
#13:41:30gmcharltsounds good
#13:45:04tsbereIs the server set up to do email at all?
#13:45:29tsbereThe errors "nobody to mail" didn't show up, but I also don't see much happening email wise
#13:45:57gmcharltno; go ahead and set up your MTA of choice
#13:46:28tsbereWe got any smart host we should be using?
#13:47:08gmcharltphasefx ^^ do you know what the new webserver is using? or what penguin used, for that matter?
#13:47:24phasefxpostfix
#13:47:32phasefxfor both
#13:47:53gmcharltwhat smart host, if any?
#13:48:03phasefxerrr, lemme see
#13:48:55phasefxI don't see mention of a smarthost in /etc/postfix/main.cf
#13:49:15tsbereLooks like there is an exim piece installed
#13:49:19phasefxrelay host?
#13:49:40tsbereRelay host sounds like what we may want
#13:49:46phasefxrelayhost = 216.154.195.232
#13:49:57phasefxthat's the new server, let me compare with penguin
#13:50:33phasefxsame thing
#13:51:56tsbereGonna swap out the exim4 for postfix. I know how to configure postfix, and the others are using it.
#13:52:18phasefx likes postfix
#13:52:26gmcharltthat's fine; exim4 was just what came by default with the VM that csharp created
#13:52:51tsbereWhat do we want to label it? git.evergreen-ils.org?
#13:53:03tsbereOr the default eg-git.georgialibraries.org?
#13:53:15gmcharltgit.evergreen-ils.org
#13:53:56gmcharltin fact, go ahead and teach the box it's git.evergreen-ils.org hostname
#13:57:08tsbereok
#14:00:15edoceo has joined #evergreen
#14:01:59gmcharltok, the SVN repos for Evergreen and OpenSRF are now read-only
#14:02:11gmcharltthem as wants to commit code, please start using Git now
#14:03:00tsbereNot usually happy to see errors in mail logs. "Recipient address rejected: Service is unavailable; from=<git@git.evergreen-ils.org> to=<tsbere@mvlc.org>" (we greylist)
#14:08:31tsberegmcharlt: We may wish to consider setting up the hook to email both of us on gitolite-admin changing
#14:08:41gmcharltagreed
#14:09:09tsbereAlt: Tell it to email whatever list we both end up on anyway
#14:12:12tsbereI think we need to pick an email prefix, or we will get [GIT] tacked on. But the commits mailing lists I think add their own prefix.
#14:16:03gmcharltthey do; let's let run with the [GIT] prefix for now to make it clear to anybody to reads the commits lists but not open-ils-dev or #evergreen
#14:16:11eeeviltsbere: no need for a new patch, just mention the branch and the update, methinks
#14:17:27tsbereeeevil: Was so much in "configuring git" mode I had to think for a moment to realize what you were replying to. Heh.
#14:18:03gmcharltwell, one could stick the branch and the commit hash in the subject lines of the git emails too ;)
#14:18:21eeevil:)
#14:19:12tsbere waits for his test message to make it through the greylister here
#14:19:36tsbereThat, and I am waiting for hedwig to try again.
#14:19:49tsbereNo clue what it uses for retry intervals.
#14:20:15tsbereWho has access to make sure the commit mailing lists accept git@git.evergreen-ils.org as a sender?
#14:20:37gmcharltphasefx ^^
#14:21:05eeevilthat's csharp's
#14:21:39phasefxlooks like I have access too
#14:23:53phasefxI could create a subscription and set it to nomail.. also seen a way to allow mails from non-subscribed folks to always go through, but only once I see something of theirs in the moderator queue
#14:24:04phasefxnot much of a mailman admin, alas :)
#14:24:40tsberephasefx: I can help you there.
#14:25:11tsberephasefx: Privacy Options->Sender Filters, List of non-member addresses whose postings should be automatically accepted.
#14:25:15phasefxfound it, privacy options, sender filters
#14:25:28phasefxList of non-member addresses whose postings should be automatically accepted
#14:26:16tsbereI would suggest not removing the svn one for the open-ils-commits list, as I think ILS-Contrib is still svn.
#14:26:37phasefxdidn't see any entries there, they may be set up as subscriptions
#14:26:42tsbereCould be.
#14:26:53tsbereThe list could not reject by default too. >_>
#14:26:54phasefxit is, nomail
#14:27:26tsbere prefers using the "non-subscriber" config than nomail subscriptions
#14:27:50phasefxshould be good to go for both lists
#14:28:20tsbereAnyone know what hedwig is set up for on a retry interval? Seems to be taking a while.
#14:29:54tsbereI suppose if it is going to try after 30 min or so it isn't time yet.
#14:32:04tsbereOh, cool, there it is!
#14:32:20tsberegmcharlt: Apparently it defaults to [SCM], not [GIT]. Do we want to change it to [GIT]?
#14:32:35gmcharltyes
#14:33:51tsbereAlso, do we want full patches?
#14:33:59tsbereIt doesn't default to that, now that I look
#14:34:06gmcharltphasefx: (since there's no MX for evergreen-ils.org) could you set up a mail alias to forward mail sent to gitadmin@evergreen-ils.org to me and tseber?
#14:34:32gmcharlttsbere: yes to full patches for the sake of consistency
#14:34:33phasefxsure thing
#14:36:13phasefxsent a test email
#14:37:10phasefxbleh, wrong email address :)
#14:37:18gmcharlt:)
#14:38:19gmcharltphasefx: got it
#14:38:44tsberephasefx: I have things stuck in greylister, will eventually get them.
#14:39:19tsberegmcharlt: Shall I add that to the email config for the gitolite-admin repo while I am in the conf anyway?
#14:39:44gmcharlttsbere: please
#14:40:41eeevil waits for svn-remote to trickle in...
#14:46:42gmcharlt@later tell dbs what shall we do with the bzr mirror on launchpad?
#14:46:42pinesol_greengmcharlt: The operation succeeded.
#14:48:25tsbereI think I got things correct for the email stuff. Someone will need to actually commit something, somewhere, to find out, I guess.
#14:48:33gmcharltone it
#14:50:08tsbereShould we add the nice new email as a reference on http://evergreen-ils.org/dokuwiki/doku.php?id=dev:git ?
#14:50:24gmcharltyep
#14:50:40tsbereShall I, or will you?
#14:50:47gmcharltI'm in there now
#14:51:47tsbereOk. I just noticed I am not logged in. Hmmm. And I think I left the password at work.
#14:52:33tsbereMeh. Can deal with that later.
#14:53:48gmcharltok, I've pushed a change; let's see if it comes in
#14:54:58gmcharltand it's arrived
#14:55:01gmcharlttsbere++
#14:57:28tsbereAhhh, whitespace changes. Great for testing things like this.
#14:59:38tsbereI should now go alter our "pull from svn" setup to, well, stop pulling from svn.
#15:01:32gmcharltmoodaepo: bshum: around?
#15:04:39gmcharltor phasefx: could you update the downloads page to point the the gitweb links instead of SVN?
#15:07:05tsberegmcharlt: I made a change to the admin repo. You should have gotten an email (I did :D)
#15:07:12gmcharltyep, I did too
#15:07:49tsbereI dislike the prefix being right against the rest of the subject. Figured you wouldn't mind.
#15:09:16gmcharltnot at all
#15:19:43phasefxgmcharlt: Downloads page updated
#15:21:00gmcharltwho here is an ohloh admin for Evergreen?
#15:24:46gmcharltphasefx: tsbere: will Open-ILS/xul/staff_client/defaults/preferences/prefs.js need to be adjusted (see starting with line 13)
#15:25:28tsberegmcharlt: I have to think of a new way to handle auto-version for trunk (master?) in the staff client code too.
#15:25:45tsberegmcharlt: And I think there is an about page somewhere using svn info as well
#15:25:51phasefxyeah
#15:29:53phasefxgmcharlt: I get a password prompt trying to ssh git@git.esilibrary.com with my batrepo key
#15:30:22phasefxah, phasefx user works
#15:30:49phasefxbut I need to use git@ per the Quick start instructions on the wiki?
#15:30:59gmcharltyes
#15:31:13gmcharltthough git@evergreen-ils.org will work better for your purposes than git@git.esilibrary.com ;)
#15:31:31phasefxindeed :) was using the right one
#15:33:33phasefxif I want to add another public key, where do I put it on that box?
#15:33:57tsberefor git@?
#15:33:58gmcharltyou email it to gitadmin@evergreen-ils.org
#15:34:09phasefxcool deal
#15:34:26tsbereme and/or gmcharlt have to add it to the admin repo. One of the few annoyances.
#15:39:53gmcharltgrabbing phasefx's new key
#15:41:11gmcharltand done
#15:43:45tsbereIn addition to the prefs.js, we need to update Open-ILS/xul/staff_client/chrome/content/main/about.html at a min. I am thinking about how to handle the staff client makefile now.
#15:46:34phasefxbtw, gmcharlt++ tsbere++
#15:52:23bwgkennedy has joined #evergreen
#15:53:27bwgkennedy has left #evergreen
#15:58:38tsberephasefx: What do you think of this for an auto-version? 0master.4e00755
#15:58:58tsbereAfter the . changing, obviously
#15:59:11tsbere could also try and make the "master" part of that be the current branch name
#15:59:32gmcharltcurrent branch name would be nice
#15:59:36phasefxI have no strong feelings there. Can Mozilla still do meaningful comparisons with the version check?
#16:00:25phasefx must jet for a bit
#16:03:32tsberephasefx: So long as that first piece is "0" I don't see an issue. How often do you auto-update dev build extensions? That is probably the only time it will matter.
#16:09:46tsberegmcharlt: Normally I would poke phasefx for this, but he jetted for a bit. Dropped some changes to my installer branch for removing some of the SVN-isms in the staff client Makefile.
#16:10:11tsbere hasn't decided what might be good for the prefs.js file or the about.html file yet
#16:10:54gmcharlt takes a look
#16:11:22tsbereOh, I also touched the readme file. Figure we should stop referring to "trunk" when the branch is "master"
#16:17:06gmcharltpushed
#16:17:58gmcharltand congrats, you're officially the first patch author to have their changed accepted (a) under the new regime and (b) without the committer having to remember to add in the author's name
#16:18:08tsbereheh
#16:18:28tsberegit++
#16:18:31tsberegmcharlt++
#16:19:48tsbereI may talk to Dyrcona monday about possibly rigging up our repos to push our branches automatically to a MVLC/Evergreen repo. Which I would have to rig up, of course. I figure it is both a good way to learn about more post-receive hook goodness and a decent idea for keeping things we are working on visible.
#16:20:08gmcharltyeah
#16:20:21gmcharltand probably now's a good time to talk about naming conventions for repos
#16:20:29gmcharltI suggest somethign like
#16:20:32tsbereTrue. Also, would we want to put a copy of one of the SIPServer repos up?
#16:20:46gmcharltevergreen/mvlc/Evergreen.git
#16:21:18gmcharlti.e., evergreen (lower case as a cheap way of keeping the "official" repos at the top of the gitweb list), then org/individual, then repo name
#16:21:36gmcharltevergreen/mvlc.git would be OK too, I suppose
#16:21:44tsbereI would be tempted to use "mirror" instead of "evergreen"
#16:21:49gmcharltsounds good
#16:22:01tsbereso mirror/mvlc/Evergreeen.git and mirror/mvlc/OpenSRF.git could live next to each other in the list
#16:22:05tsbereFor example
#16:22:11gmcharltyeah, that works for me
#16:22:41gmcharltand sipserver counts as a related project, so it would be fair game for git.evergreen-ils.org
#16:22:44tsbereWe have multiple repos, though. Will probably rig it so that the branches are auto-prefixed with tsbere/ and jason/ (or dyrcona/, whichever he picks)
#16:23:01gmcharltyeah
#16:23:13gmcharltat that point it would be up to the organization to manage their repos and branches as they see fit
#16:23:51tsbereThat also brings up mailing stuff. What would the policy be for mailing list based updates to the secondary repos?
#16:24:13tsbereAnd, for repos not mirroring a remote, would we want a different starting folder?
#16:26:32tsbere thinks that there is a lot to think about still
#16:29:20gmcharlttsbere: for an active, non-mirror repo, I still like lowercaseproject/organizationorindividiual.git
#16:29:33tsbereSounds good
#16:29:34gmcharltor lowercaseproject/organization/subjectprojectorindividual.git
#16:30:09gmcharltas far as mailing lists - I say if somebody wants their commits to be mailed somewhere, we do it for them
#16:30:20gmcharltbut reserve open-ils-commits and opensrf-commits just for the official repos
#16:32:15tsbereok
#16:32:21tsbereI figured that would be the general case
#16:32:47gmcharltthough probably wouldn't hurt to make the requestor send a confimration that the recipient address actually wants the commit messages
#16:33:03tsberePreferably, it goes to an opt-in mailing list
#16:33:11gmcharltyeah
#16:34:13gmcharltand on our end, be ruthless about disabling it if the recipient list starts ending back bounces
#16:36:07tsbereTrue. BTW, should I document how to do that via the config file?
#16:39:04gmcharltplease
#16:39:25gmcharltbshum: I'm setting up a repo for the website project for you now
#16:39:42bshumgmcharlt: Sounds good.
#16:40:01gmcharlttime to make git-svn do my bidding
#16:45:12bshumFor the documentation page on the website, there's a link called "watch us work" pointing to SVN timeline. What should the new git equivalent be?
#16:46:48bshumI could see http://git.evergreen-ils.org/?p=Evergreen.git;a=summary being useful in that place.
#16:47:02gmcharltbshum: yes
#16:47:03tsberegmcharlt: I added the basic docs to the top of the conf file. I figured they should be prominent.
#16:47:03bshumOr there's a trac looking at the git stuff too
#16:47:07gmcharltgitweb can also generate RSS feeds
#16:47:14gmcharlttsbere++
#16:47:18gmcharltand bshum: http://git.evergreen-ils.org/?p=Evergreen_Website.git;a=summary
#16:47:36tsbereI also included the naming notes, if you haven't read the email yet
#16:47:59gmcharltbshum: I gotta go in the next few minutes, but if you have ten, I can give you a crash course
#16:48:18bshumgmcharlt: That would be great actually.
#16:48:25bshumI'm about to try cloning the repo
#16:48:37bshumPoking at it with my Mac first.
#16:48:38tsbereAside from eating shortly I can also help out with git related learning.
#16:48:43gmcharltok; since you're pushing to it, you want to use the following as a clone address
#16:48:53gmcharltgit@git.evergreen-ils.org:Evergreen_Website.git
#16:52:03bshumOkay.
#16:54:47gmcharltso then, after cloning, you should create a working branch for chance (working in your local repo's copy of the master branch has pitfalls for git newbies)
#16:54:53gmcharltgit checkout -b working
#16:55:15gmcharltand you'll want to make sure git knows your name and email addresses for signoffs
#16:55:24gmcharltin the git repo, do
#16:55:38gmcharltgit config user.name "Your Name"
#16:55:54tsbereAlternatively, from anywhere, do that, but with --global after config
#16:55:55gmcharltgt config user.email "you@example.org"
#16:56:43gmcharltyeah, doing it global works well for people who (unlike me) just need one identity for the Git commits and signoffs
#16:56:48bshumOkay, switched to new branch working
#16:57:01gmcharltnext step is to make a change
#16:57:39gmcharltand once you've made your change
#16:57:45gmcharltgit commit -a -s
#16:57:58bshumOkay.
#16:58:03gmcharlt-a to tell git to commit changes you've made to all of the files it knows about
#16:58:08tsberefair warning, if you make a *new* file, you will need to git add <file>
#16:58:08gmcharlt-s to append your signoff
#16:58:51tsbere often tests VCS systems with adding a dummy temp file
#16:58:55bshumHmm, vi for the commit message, fun times.
#16:59:04tsberebshum: You can change that.
#16:59:15bshumtsbere: I definitely prefer nano in command line.
#16:59:58gmcharltgit config --global core.editor /path/to/nano
#17:00:15tsberegmcharlt++
#17:00:28tsbere was trying to recall the setting name
#17:01:07eeevilthat's one thing that continually frustrates me
#17:01:19eeevilremembering the config paths
#17:01:42gmcharltbshum: so after commiting your change
#17:02:19gmcharltyou next want to fetch updates (let's assume for the sake of argument that moodaepo has been silently changing something while we've been chatting (and silently breaking into the git server to do that ;) )
#17:02:24gmcharltso, one way is
#17:02:27gmcharltgit pull origin master
#17:02:37gmcharltpull the *master* branch from the origin repository
#17:03:08bshumOkay.
#17:03:20gmcharltnow, it should tell you that it's already up to date
#17:03:20bshumAlready up-to-date (which is to be expected)
#17:03:23gmcharltso now to push:
#17:03:28gmcharltgit push origin working:master
#17:03:46gmcharltpush to the remote named origin from your working branch to the remote's branch named master
#17:04:07gmcharltand ...
#17:04:08gmcharltbshum++
#17:04:31gmcharltbshum: so how are changes getting propagated to the webserver?
#17:04:50gmcharltare you doing that manually, or is there some kind of automatic push out from svn that needs to be changed over to git?
#17:04:55eeevilgmcharlt: are we leaving the ils-contrib repo alone for now?
#17:04:59bshumgmcharlt: I'm not sure of all the details, but I got over there to the web server and do svn update to pull down the changes
#17:05:16bshumSo I guess we have to redo how that works over there
#17:05:23gmcharltyep
#17:05:49gmcharlteeevil: yes; I've asked for SSH keys from ILS-contrib committers, but am also splitting it up a bit
#17:05:58gmcharlte.g., the website repo conversation I'm having with bshum right now
#17:06:43eeevilgmcharlt: ahh, perfect ... keeping history somehow?
#17:07:00gmcharlteeevil: yep, git-svn handles that beautifully
#17:09:37bshumLooks like /var/www/open-ils.org on Lupin is a symlink to /root/svn/ILS-Contrib/evergreen-ils.org/
#17:10:27gmcharltthen you'll need to set up a git clone (of git://git.evergreen-ils.org/Evergreen_Website.git)
#17:10:32bshumYep.
#17:10:33eeevilbooooo (says the guy what doesn't maintain it)
#17:10:35gmcharltchange the symlink over
#17:11:06gmcharltand add a crontab that does a git pull periodically (if you want to automate it), or just do the git pull manually (if you don't want to automate it)
#17:12:10bshumHeh
#17:12:20bshumGuess I should install git on Lupin first :)
#17:13:17tsberegmcharlt / bshum: FYI, I usually do git checkout -b name origin/master - That way I can be lazy and just type "git pull". The origin/master is the "Tracking branch" in that case.
#17:24:13bshumWebsite changed to use git clone now.
#17:24:23bshumI'm moving the downloads folder stuff into the place though
#17:27:19gmcharlt turns into a pumpkin
#17:27:22gmcharltthanks everybody
#17:27:24bshumThanks gmcharlt
#17:29:24tsberebshum: If you have other questions, let me know.
#17:29:42bshumtsbere: Thanks, I'm sure I'll have plenty. Very much the git newbie.
#17:29:52bshumWell, version control in general really.
#17:30:47tsbereSo was I a few months ago. Now I am co-admining a git server. Isn't that hard to pick up if you use it for something you are dealing with a couple times a week.
#17:34:05bshumOnce you commit something
#17:34:19bshumDo you have to do anything on the local side?
#17:37:22tsbereWe
#17:37:24tsbere...
#17:37:36tsberewell, if you want someone else to be able to see it you need to push it to somewhere public
#17:37:45bshumAh right.
#17:37:55bshumI think I already did that.
#17:38:19tsbereYou can also make multiple branches locally and then use git merge before pushing, if you want
#17:39:16tsbereSay you were working on two different changes, each in a branch. You commit them both. You could then git checkout master; git pull origin master; git merge branch1; git merge branch2; git push origin master
#18:33:44tsberephasefx / gmcharlt / eeevil / whoever: Missed "Trunk" in windowssetup.nsi. Pushed an update to my installer branch, if anyone wants to merge it.
#19:02:13edoceo has quit IRC
#19:46:16edoceo has joined #evergreen
#20:48:33gmcharlttsbere: pushed
#21:01:53tsberegmcharlt++
#21:03:35tsbere updated a few things on the dokuwiki
#21:03:56tsbereFound that opensrf git was referring to evergreen's, and it said subversion instead of git
< Friday, May 13th, 2011Raw Log FileSunday, May 15th, 2011 >