| Time |
Nick |
Message |
| 03:23 |
bshum |
kmlussier++ # more plugins! |
| 04:56 |
pinesol_green |
Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
| 10:03 |
|
kmlussier joined #evergreen |
| 10:18 |
jl- |
morning |
| 10:27 |
jl- |
dbs ping |
| 12:08 |
dbs |
jl-: don't just ping me, paste your steps from "git clone" through "git push" into a pastebin and share it here / send it to the gitadmin email address so that you can have a broader audience of helpers. |
| 12:27 |
|
zerick joined #evergreen |
| 13:29 |
|
Callender_ joined #evergreen |
| 13:32 |
|
Callender__ joined #evergreen |
| 13:34 |
|
Callender joined #evergreen |
| 13:35 |
|
gsams joined #evergreen |
| 13:38 |
|
yboston joined #evergreen |
| 14:05 |
|
ercik13 joined #evergreen |
| 15:13 |
jl- |
yboston: I'm getting the same error after a push that you had yesterday, any idea what made it work for you? |
| 15:13 |
jl- |
FATAL: W any Evergreen bwiens DENIED by fallthru |
| 15:13 |
jl- |
(or you mis-spelled the reponame) |
| 15:14 |
yboston |
funny, I am trying to make some changes to the docs through git right now |
| 15:14 |
yboston |
yesterday Galen did something with the Git config, and it started working |
| 15:14 |
jl- |
i it working for you now? |
| 15:14 |
yboston |
though I had a small errror in my Git config |
| 15:15 |
jl- |
can you cat your .git/config |
| 15:15 |
yboston |
I had originally cloned my repo as... |
| 15:15 |
yboston |
git clone http://git.evergreen... |
| 15:15 |
yboston |
and it should have been... |
| 15:15 |
yboston |
git clone git git.ev |
| 15:15 |
yboston |
Do you remember how you cloned your repo? |
| 15:16 |
jl- |
I think with http |
| 15:16 |
yboston |
let me paste my config |
| 15:17 |
jl- |
ok |
| 15:17 |
yboston |
[remote "origin"] |
| 15:17 |
yboston |
url = gitgit.evergreen-ils.org:Evergreen |
| 15:18 |
yboston |
fetch = +refs/heads/*:refs/remotes/origin/* |
| 15:18 |
yboston |
[branch "master"] |
| 15:18 |
yboston |
remote = origin |
| 15:18 |
yboston |
merge = refs/heads/master |
| 15:18 |
yboston |
[remote "working"] |
| 15:18 |
yboston |
url = git://git.evergreen-ils.org/working/Evergreen.git |
| 15:18 |
yboston |
fetch = +refs/heads/*:refs/remotes/working/* |
| 15:18 |
yboston |
pushurl = gitgit.evergreen-ils.org:working/Evergreen.git |
| 15:18 |
yboston |
for the record, I have my set up so I can push to most fo the working repo... |
| 15:18 |
yboston |
but I also can push to anything under the main repo's "docs" directory so I can update the documentation |
| 15:19 |
jl- |
yes that's what I'm trying let's see |
| 15:19 |
yboston |
you are pushing to the docs in the main repo? |
| 15:23 |
jl- |
yes |
| 15:23 |
jl- |
git push origin master |
| 15:23 |
jl- |
is that what you are doing for the docs? |
| 15:24 |
yboston |
I beleive so, but to be clear, I was given special permission from my work with DIG to be able to push tot he main repo's "docs" direcotry |
| 15:24 |
jl- |
ah |
| 15:24 |
jl- |
that is probably it then |
| 15:24 |
yboston |
you may not have that permission, thouhg you have permison to add to working repo |
| 15:24 |
jl- |
gotcha |
| 15:24 |
yboston |
I made a note to reach out to you on monday to wee where you wanted to place your new docuemntationw ithin the offical docs |
| 15:25 |
yboston |
then you suddenly started asking me questios |
| 15:25 |
yboston |
*questions |
| 15:25 |
jl- |
funny :) |
| 15:25 |
yboston |
yes |
| 15:26 |
yboston |
BTW< it would be nice to have your help with documentation, even if it is just a little bit of help |
| 15:26 |
jl- |
absolutely, I'd be happy to help |
| 15:26 |
jl- |
here's what I added: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=blob;f=docs/admin/staff_client-reset_lost_password.txt;h=c51b0522ea265fd39b88e5958d17c8b83e11379f;hb=5234b37d5871162c85de40e9ba6c6062b51f123c |
| 15:26 |
yboston |
yes, I just looked it over like 20 minutes ago |
| 15:27 |
yboston |
two things |
| 15:27 |
jl- |
my only concern is, I'd like it to get linked to my github |
| 15:27 |
jl- |
I see other people commit and they are linked (galen said something about the email being used as the identifier) |
| 15:27 |
yboston |
1) I think, but I am not sure, did you put that change in the "working repo" master branch? |
| 15:27 |
yboston |
if so, I suggest that next time you make a "topic" branch with your changes |
| 15:28 |
yboston |
2) have you thought where you would like us to place that information in the offical docs? like what chapter / page? it is OK if you have not decide yet |
| 15:28 |
jl- |
it's I think it's in user/bwiens/working_branch |
| 15:28 |
jl- |
topic branch makes sense |
| 15:29 |
jl- |
good idea, I'll have to have a close look at the official docs to see where it makes the most sense |
| 15:30 |
yboston |
I see it now that you made a "topic branch" under your username. Though I would choose a more descriptive branch name instead of :working_branch" next time |
| 15:30 |
jl- |
yes I can call it documentation or something |
| 15:30 |
yboston |
also, I have not explored how to have github notice your changes to the main or working repo |
| 15:31 |
yboston |
for the record, in case you end up doing more documentation fizes/update, I would suggest your brnach names give a little hint of the type of docs like "documentation_change_password" |
| 15:32 |
yboston |
in case you end up doing a lot of brnaches, but if you only do a few, don't worry too much about the name |
| 15:33 |
jl- |
sounds good |
| 15:33 |
yboston |
BTW< it would be nice to know how to make github track my commits to the EG repo's, I will pay attention how others make it work. THough I may need to be more careful with the email addresses I use when committing |
| 15:33 |
jl- |
I'm hoping that as I am migrating data I will find more useful changes |
| 15:34 |
jl- |
yes gmcharlt mentioned that the email is the identifier for that |
| 15:34 |
jl- |
which in my case, is the same, not sure when/how it will actually be linked |
| 15:40 |
dbs |
yboston: is jl- part of DIG and therefore should be part of the docwriters group for commit purposes? |
| 15:41 |
dbs |
jl-: you need to "git commit -s" in the future; your Author line is preserved but generally we also want the "-s" for the Signed-off-by line as well |
| 15:42 |
yboston |
most DIG members acknowlege that "DIG membership" is very casual. Sometimes it is argued that just beng on our mailing list is good enough. |
| 15:43 |
yboston |
dbs: most DIG members acknowlege that "DIG membership" is very casual. Sometimes it is argued that just beng on our mailing list is good enough. |
| 15:43 |
dbs |
yboston: I mean for purposes of pushing to the master repo. I'd suggest giving jl- a chance to work through a few branches before we grant commit access |
| 15:44 |
yboston |
dbs: jl- is very new to EG, but already he has impressed me by following intrutiosn and putting together asciidoc docuemtnation on the working repo. that is an impressive start |
| 15:44 |
dbs |
basically the gitadmins will grant that direct commit access once DIG says "do it" |
| 15:45 |
yboston |
yes, I was going to approach him later this week to ask him, but I did not want to sacre him off :) |
| 15:45 |
yboston |
*scare |
| 15:45 |
dbs |
but we don't want git learning to occur on the master repo; stick with working for a few rounds |
| 15:45 |
yboston |
that is what I was thinking |
| 15:46 |
jl- |
that's fine, thanks for approaching me I like being involved |
| 15:46 |
dbs |
jl-++ |
| 15:47 |
yboston |
dbs: I also was thinking something reated last week, I came up with a very loose process to anounce on the DIG mailing list when we wabt to publicly ask someone to get docuemntation privileges to the main repo |
| 15:47 |
yboston |
dbs: and it was that the person needs to have been succesful in pushing topic branches to working first |
| 15:49 |
yboston |
dbs: I mean that I had already come up with a process to anounce on the DIG list to give someone Git priveleges, but now I want to add that they need to have docuemented expirince with the workign repo |
| 15:49 |
yboston |
dbs: seeign jl-'s work reminded me of how I want things to progress int he future |
| 15:56 |
dbs |
yboston++ |
| 16:14 |
bshum |
Regarding github linking of activities, I think that once commits are added to the main master branch or such, it'll begin to show up for activity with the mirrored Evergreen master repo. The working branches are not tracked in the same way initially. |
| 16:17 |
bshum |
jl-: I might recommend setting up your git name / email. This is described on the dev:git page -- http://wiki.evergreen-ils.org/doku.php?id=dev:git#quick_start_for_evergreen_contributors |
| 16:18 |
bshum |
There's lot of good information on that page for getting started with git usage and pushing branches too. |
| 16:18 |
* bshum |
disappears back into the mists |
| 16:20 |
jl- |
bshum: I think the lack of signoff |
| 16:20 |
jl- |
resulted in it |
| 16:20 |
jl- |
I'm going to delete the branch, create a topic branch and commit with a signoff |
| 16:21 |
jl- |
and it makes sense that the working branches might not be tracked |
| 17:09 |
|
Callender_ joined #evergreen |
| 17:14 |
jl- |
done, bbl |
| 17:24 |
yboston |
I want to start a draft wiki page that lists info on pinesol_green. Is this the original name of this bot? I am trying to google information on it |
| 17:26 |
jcamins |
yboston: pinesol_green is a supybot. |
| 17:28 |
yboston |
jcamins: thanks |
| 17:32 |
jl- |
yboston btw, I think if you add yamilyamil.com to your emails on github, it will link the master commits |
| 17:32 |
yboston |
jl-: that is what I was thinking, though I rather have two seperate emails registered with github, but I doubt I can have that |
| 17:32 |
yboston |
jl-: thanks |
| 17:32 |
jcamins |
yboston: you got a domain with just one name? Lucky. |
| 17:33 |
jcamins |
yboston: and you can have multiple. |
| 17:33 |
yboston |
jcamins: the advantages of having a pretty unqiue name |
| 17:33 |
yboston |
to quote arrested development: "there are dozens of us" |
| 17:33 |
jl- |
hehe |
| 17:34 |
jcamins |
Hehe. |
| 17:34 |
yboston |
seriously, in latin america there are hundreds. |
| 17:38 |
yboston |
jl-: thanks for the tip about multiple email. I just updted my account withthe second address |
| 17:43 |
jl- |
no problem, I was curious about this myself :) |
| 17:46 |
yboston |
@help |
| 17:46 |
pinesol_green |
yboston: (help [<plugin>] [<command>]) -- This command gives a useful description of what <command> does. <plugin> is only necessary if the command is in more than one plugin. |
| 17:46 |
yboston |
@help marc |
| 17:46 |
pinesol_green |
yboston: (marc look up field or field/subfield combo in MARC docs) -- eg. @marc 245 or @marc 245 a |
| 17:46 |
yboston |
@list |
| 17:46 |
pinesol_green |
yboston: Admin, Anagram, Assorted2, Blame, Bugtracker, Channel, ChannelLogger, Config, Dunno, Encyclopedia, Games, Git, Herald, Insult, Karma, Later, LoveHate, MARC, Math, MeetBot, Misc, Note, Owner, Praise, Quote, RSS, Reply, Seen, Status, Time, Todo, Twitter, User, and Weather |
| 17:52 |
bshum |
@list Assorted2 |
| 17:52 |
pinesol_green |
bshum: bartender, coffee, dessert, developer, dnd, gamma, librarian, someone, sortinghat, swill, tea, and who |
| 17:52 |
yboston |
@marc 856 |
| 17:52 |
pinesol_green |
yboston: The information needed to locate and access an electronic resource. The field may be used in a bibliographic record for a resource when that resource or a subset of it is available electronically. In addition, it may be used to locate and access an electronic version of a non-electronic resource described in the bibliographic record or a related electronic resource. (Repeatable) (1 more message) |
| 17:52 |
bshum |
@more |
| 17:52 |
pinesol_green |
bshum: Error: You haven't asked me a command; perhaps you want to see someone else's more. To do so, call this command with that person's nick. |
| 17:52 |
bshum |
@more yboston |
| 17:52 |
pinesol_green |
bshum: [a,b,c,d,f,h,i,j,k,l,m,n,o,p,q,r,s,t,u,v,w,x,y,z,2,3,6,8] |
| 17:53 |
bshum |
yboston: So when the command ends with (1 more message) or however many messages, just go for @more to see the remainder of the message. |
| 17:53 |
* yboston |
is creating a wiki page about pinesol_green for others to controbute too |
| 17:53 |
yboston |
*to |
| 17:53 |
yboston |
thanks |
| 17:58 |
yboston |
Here is the wiki page that I started. Feel free to add to it. I will post it to the dev list for others to make changes too |
| 17:58 |
yboston |
http://wiki.evergreen-ils.org/doku.php?id=community:using-pinesol_green |
| 18:25 |
gsams |
would someone be willing to hook me up with an account for the wiki? |
| 18:43 |
|
kmlussier joined #evergreen |
| 18:44 |
kmlussier |
@dessert bshum |
| 18:44 |
* pinesol_green |
grabs a big dish of Banana Split and sends it sliding down the dessert bar to bshum |
| 18:44 |
kmlussier |
:D |
| 18:48 |
kmlussier |
@later tell bshum I have a couple more desserts to add when you have a chance. |
| 18:48 |
pinesol_green |
kmlussier: The operation succeeded. |
| 18:53 |
bshum |
kmlussier: Okay, just let me know later. |
| 18:53 |
bshum |
kmlussier: I'd like to try modifying it someday to use a database or similar so that people can add their own desserts. Someday. |
| 18:53 |
kmlussier |
That could be interesting. |
| 19:00 |
jl- |
http://chapul.com/ an energy bar with cricket flour |
| 19:01 |
bshum |
@later tell gsams I sent you an email with wiki account. |
| 19:01 |
pinesol_green |
bshum: The operation succeeded. |
| 19:17 |
gsams |
bshum: thanks! |
| 19:58 |
|
Callender joined #evergreen |
| 20:28 |
|
zerick joined #evergreen |
| 20:31 |
|
zxiiro joined #evergreen |
| 22:52 |
|
Callender_ joined #evergreen |
| 23:23 |
csharp |
@sortinghat |
| 23:23 |
pinesol_green |
Hmm... csharp... Let me see now... HUFFLEPUFF! |
| 23:24 |
csharp |
@coffee [someone] |
| 23:24 |
* pinesol_green |
brews and pours a cup of Panama Esmeralda Especial, and sends it sliding down the bar to hopkinsju |
