[PATCH 02/15] for-each-ref: don't print out elements directly

2013-07-09 Thread Ramkumar Ramachandra
From: Nguyễn Thái Ngọc Duy Currently, the entire callchain starting from show_ref() parses and prints immediately. This inflexibility limits our ability to extend the parser. So, convert the entire callchain to accept a strbuf argument to write to. Also introduce a show_refs() helper that call

Re: [PATCH 02/15] for-each-ref: don't print out elements directly

2013-06-04 Thread Duy Nguyen
On Wed, Jun 5, 2013 at 6:13 AM, Junio C Hamano wrote: > Ramkumar Ramachandra writes: > >> From: Nguyễn Thái Ngọc Duy >> >> Currently, the entire callchain starting from show_ref() parses and >> prints immediately. This inflexibility limits our ability to extend the >> parser. So, convert the e

Re: [PATCH 02/15] for-each-ref: don't print out elements directly

2013-06-04 Thread Junio C Hamano
Ramkumar Ramachandra writes: > From: Nguyễn Thái Ngọc Duy > > Currently, the entire callchain starting from show_ref() parses and > prints immediately. This inflexibility limits our ability to extend the > parser. So, convert the entire callchain to accept a strbuf argument to > write to. Als

[PATCH 02/15] for-each-ref: don't print out elements directly

2013-06-04 Thread Ramkumar Ramachandra
From: Nguyễn Thái Ngọc Duy Currently, the entire callchain starting from show_ref() parses and prints immediately. This inflexibility limits our ability to extend the parser. So, convert the entire callchain to accept a strbuf argument to write to. Also introduce a show_refs() helper that call