Re: [sage-combinat-devel] Re: sage-combinat move to git

2013-11-09 Thread Anne Schilling
Dear Sage Days 54 Participants, Thanks again all for coming to Davis and working on the new git workflow together. Andrew and Volker, thank you for coming and teaching us the basics! The overall sentiment was that the new workflow is a great improvement over the old workflow. Soon we won't have

Re: [sage-combinat-devel] Re: sage-combinat move to git

2013-11-09 Thread Anne Schilling
> Sorry I had to leave yesterday during the discussion > of the workflow/searching. It seems like you made a lot > more progress on the document. Yes, and more this morning! I will send out an e-mail in a second when the page is semi-stable. One thing that Travis and I tried out in practice after

Re: [sage-combinat-devel] Re: sage-combinat move to git

2013-11-09 Thread Mike Zabrocki
Thanks, I thought the * was to complete the name if I didn't know the ending. -Mike -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-combinat-devel+un

Re: [sage-combinat-devel] Re: sage-combinat move to git

2013-11-09 Thread Anne Schilling
Hi Mike, You can get do the search remotely via $ git log --remotes='origin/public/combinat/sf/sp_orth*' ^origin/master --oneline 8864ef1 Added files. 226c37a Initial version of symplectic and orthogonal basis for symmetric functions. Note there is a * after the name. Best, Anne On 11/9/13

[sage-combinat-devel] Re: sage-combinat move to git

2013-11-09 Thread Mike Zabrocki
I guess that I should make it clearer that the first time I searched the log with: $ git log to find the commit message by Travis by looking through all of them to find the one relevant to the branch I was interested in. It wasn't until later that I realized that could checkout the branch first an

[sage-combinat-devel] Re: sage-combinat move to git

2013-11-09 Thread Mike Zabrocki
Hi, Sorry I had to leave yesterday during the discussion of the workflow/searching. It seems like you made a lot more progress on the document. I was reading the searching section and I still don't quite see how to tell who wrote the code or who posted: origin/public/combinat/sf/sp_orth I even

Re: [sage-combinat-devel] Re: emacs

2013-11-09 Thread Nicolas M. Thiery
On Sat, Nov 09, 2013 at 12:16:37AM -0800, Anne Schilling wrote: > > Yes, that's what I mean by "main contact" above. Give an immediate > > visual hint, when I see a branch, about "someone" to get in touch > > with. > > When you have a specific branch in mind you can easily find out by looking > at

Re: [sage-combinat-devel] Re: emacs

2013-11-09 Thread Anne Schilling
> Yes, that's what I mean by "main contact" above. Give an immediate > visual hint, when I see a branch, about "someone" to get in touch > with. When you have a specific branch in mind you can easily find out by looking at its log. Best, Anne -- You received this message because you are subscr