On Thursday 17 August 2017 12:58 AM, Junio C Hamano wrote:
Nothing has. Neither thread seems to have any comment from anybody
but you, and I took it as an indication that people do not think it
is a good change.
I do not find the s/branch/parameter/ too bad (although I would have
said "argument
Kaartic Sivaraam writes:
> It's been around 4 or 5 issues of 'What's cooking in git.git' and I haven't
> heard about the patches found at,
>
> http://public-inbox.org/git/<20170730111705.12444-1-kaarticsivaraam91...@gmail.com>
>
> and
>
> https://public-inbox.org/git/<20170730115908.13841-1-kaart
It's been around 4 or 5 issues of 'What's cooking in git.git' and I haven't
heard about the patches found at,
http://public-inbox.org/git/<20170730111705.12444-1-kaarticsivaraam91...@gmail.com>
and
https://public-inbox.org/git/<20170730115908.13841-1-kaarticsivaraam91...@gmail.com>
What has ha
On Mon, Aug 14, 2017 at 04:53:35PM -0700, Junio C Hamano wrote:
> * jk/trailers-parse (2017-08-10) 5 commits
> - interpret-trailers: add --parse convenience option
> - interpret-trailers: add an option to normalize output
> - interpret-trailers: add an option to show only existing trailers
> -
Here are the topics that have been cooking. Commits prefixed with
'-' are only in 'pu' (proposed updates) while commits prefixed with
'+' are in 'next'. The ones marked with '.' do not appear in any of
the integration branches, but I am still holding onto them.
The tip of 'next' has been rebuilt
5 matches
Mail list logo