On Wednesday, December 21, 2011 12:17:57 PM Jeff Garzik wrote:
> On Wed, Dec 21, 2011 at 12:14 PM, Luke-Jr wrote:
> > On Wednesday, December 21, 2011 12:12:43 PM Jeff Garzik wrote:
> >> On Wed, Dec 21, 2011 at 11:45 AM, Luke-Jr wrote:
> >> > Accepted for 0.6:
> >> > * 81807c3 (pull 719) Coinbaser
On Wed, Dec 21, 2011 at 12:14 PM, Luke-Jr wrote:
> On Wednesday, December 21, 2011 12:12:43 PM Jeff Garzik wrote:
>> On Wed, Dec 21, 2011 at 11:45 AM, Luke-Jr wrote:
>> > Accepted for 0.6:
>> > * 81807c3 (pull 719) Coinbaser
>>
>> This is not "accepted" as discussed yesterday on IRC. You need to
On Wednesday, December 21, 2011 12:12:43 PM Jeff Garzik wrote:
> On Wed, Dec 21, 2011 at 11:45 AM, Luke-Jr wrote:
> > Accepted for 0.6:
> > * 81807c3 (pull 719) Coinbaser
>
> This is not "accepted" as discussed yesterday on IRC. You need to
> find buy-in from some other miners to make sure this
On Wed, Dec 21, 2011 at 11:45 AM, Luke-Jr wrote:
> Accepted for 0.6:
> * 81807c3 (pull 719) Coinbaser
This is not "accepted" as discussed yesterday on IRC. You need to
find buy-in from some other miners to make sure this is what "they"
want, rather than just what "you" want.
--
Jeff Garzik
exM
On Tuesday, December 20, 2011 8:46:41 PM Luke-Jr wrote:
> On Tuesday, December 20, 2011 3:49:16 PM Gavin Andresen wrote:
> > I've been busy pulling patches into git HEAD for a Bitcoin version
> > 0.6, with the goal of having a Release Candidate 1 out in a couple of
> > weeks.
>
> I've rebuilt my '
On Wednesday, December 21, 2011 5:12:07 AM Mike Hearn wrote:
> Git does not produce very helpful summaries when every commit is a merge.
> Is there a way to fix that? You have to guess what a change does based on
> the name of the topic branch currently.
Not sure what you mean. Maybe `git log --no
Woohoo, 0.6.0 merging time!
I'll merge some GUI pull requests for 0.6.x this/next week.
Wladimir
On Tue, Dec 20, 2011 at 9:49 PM, Gavin Andresen wrote:
> FYI for anybody who doesn't hang out in IRC:
>
> I've been busy pulling patches into git HEAD for a Bitcoin version
> 0.6, with the goal of h
Thanks for this summary Luke.
Git does not produce very helpful summaries when every commit is a merge.
Is there a way to fix that? You have to guess what a change does based on
the name of the topic branch currently.
--
W
On Tuesday, December 20, 2011 3:49:16 PM Gavin Andresen wrote:
> I've been busy pulling patches into git HEAD for a Bitcoin version
> 0.6, with the goal of having a Release Candidate 1 out in a couple of
> weeks.
I've rebuilt my 'next' and 'next-test' branches...
git://gitorious.org/~Luke-Jr/b
9 matches
Mail list logo