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 12:34 PM, Mike Zabrocki wrote:
> 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 and then check the logs only relevant to that branch.
> 
> The command that I think should work to read the log of a branch
> without checking it out doesn't seem to work for me.
> 
> -Mike
> 
> On Saturday, 9 November 2013 14:24:18 UTC-5, Mike Zabrocki wrote:
> 
>     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 searched the logs and I didn't see the name of branch
>     but I did see:
> 
>     -----
>     commit 226c37a8561486888d0231095ac6df379aa46323
>     Author: Travis Scrimshaw <tscrim at ucdavis.edu <http://ucdavis.edu>>
>     Date: Fri Nov 8 18:59:36 2013 -0800
> 
>     Initial version of symplectic and orthogonal basis for symmetric 
> functions.
> 
>     Currently this does not work correctly because the basis do not
>     give a Hopf structure by converting to the Schur basis and
>     it is only a filtered basis, not a graded basis.
>     -----
> 
>     So I in this case I could realize that this commit message
>     is probably related to this branch, but in general the commit
>     messages are not so helpful:
> 
>     more grammar fixed
>     typo fixed
>     more doc fixes
> 
>     and I had to sift through those to find the one that I wanted. If it had
>     been committed 3 weeks ago I doubt that there would be any chance
>     that I would be able to figure out who is working on it to contact them
>     to let them know I was interested. I'm sure that there is a way to
>     resolve this issue.
> 
>     Is there a command to look up the creator of a branch?
> 
>     I found one way to (maybe) resolve this was to checkout the branch
>     and then execute the command:
> 
>     $ git log HEAD ^master
> 
>     but what didn't work was
> 
>     $ git log --remotes='origin/public/combinat/sf/sp_orth' ^origin/master
> 
>     Shouldn't this command show me the commits on that branch?
> 
>     -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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-combinat-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-combinat-devel.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to