On Monday 19 January 2009, Junio C Hamano <gitster@xxxxxxxxx> wrote
about 'What's cooking in git.git (Jan 2009, #04; Mon, 19)':
>Here are the topics that have been cooking. Commits prefixed with '-'
> are only in 'pu' while commits prefixed with '+' are in 'next'. The
> ones marked with '.' do not appear in any of the branches, but I am
> still holding onto them.
Is there anywhere you are publishing these refs? Of course, I see the
commits in 'pu', but sometimes I would like to merge something you have
in 'next'/'pu' into a branch based on 'master' or one of my local
branches, and I have to go hunting for the commit SHA.
It's not a big deal: qgit, gitk, and 'git log'+grep all solve the issue
quickly enough, and I don't want to add to your workload. I was just
hoping they were already published and I could simply add a remote to my
config to get them.
Currently, I'm just using:
* remote origin
URL: git://git.kernel.org/pub/scm/git/git.git
Remote branch merged with 'git pull' while on branch master
master
Tracked remote branches
html maint man master next pu todo
and I get this:
$ git pull origin jk/color-parse
fatal: Couldn't find remote ref jk/color-parse
--
Boyd Stephen Smith Jr. ,= ,-_-. =.
bss@xxxxxxxxxxxxxxxxx ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
http://iguanasuicide.net/ \_/
Attachment:
signature.asc
Description: This is a digitally signed message part.
