git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Couder <christian.couder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git <git@vger.kernel.org>,
	"Thomas Ferris Nicolaisen" <tfnico@gmail.com>,
	"Nicola Paolucci" <durden@gmail.com>, "Jeff King" <peff@peff.net>,
	"Jakub Narębski" <jnareb@gmail.com>,
	"Eric Wong" <normalperson@yhbt.net>,
	"Nguyen Thai Ngoc Duy" <pclouds@gmail.com>,
	"Stefan Beller" <sbeller@google.com>,
	"Michael Haggerty" <mhagger@alum.mit.edu>,
	"Ramsay Jones" <ramsay@ramsayjones.plus.com>,
	"remi galan-alfonso" <remi.galan-alfonso@ensimag.grenoble-inp.fr>,
	"Johannes Sixt" <j6t@kdbg.org>,
	"Torsten Bögershausen" <tboegi@web.de>,
	"Josh Triplett" <josh@joshtriplett.org>,
	"Lars Schneider" <larsxschneider@gmail.com>
Subject: Re: Draft of Git Rev News edition 18
Date: Mon, 15 Aug 2016 08:17:49 +0200	[thread overview]
Message-ID: <CAP8UFD2mfa2hNDknEt=bsbXVn4xSSiyVYz94KL_JPbD66QrfPg@mail.gmail.com> (raw)
In-Reply-To: <xmqqeg5rkqy6.fsf@gitster.mtv.corp.google.com>

On Sun, Aug 14, 2016 at 10:58 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Christian Couder <christian.couder@gmail.com> writes:
>
>> You can also reply to this email.
>
> I am not sure that is to be recommended, as that ends up going to
> the list, but anyway, these
>
>  - Michael's "finding better -/+ assignment in diff using indent
>    heuristic"
>
>  - Philip Oakley's updates to revision range notation documentation
>
>  - Kevin Willford's rather clever optimization on internal patch-id
>    computation that is done to exclude already-applied commit while
>    rebasing
>
> are interesting/noteworthy topics that may want to be covered in the
> discussion/review section.

Yeah, these are great topics and I would be glad if they could be
covered by someone else ;-)

  reply	other threads:[~2016-08-15  6:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-14 17:15 Draft of Git Rev News edition 18 Christian Couder
2016-08-14 20:58 ` Junio C Hamano
2016-08-15  6:17   ` Christian Couder [this message]
2016-08-14 21:10 ` Philip Oakley
2016-08-14 23:10   ` Eric Wong
2016-08-14 23:37     ` Philip Oakley
2016-08-14 23:57       ` Eric Wong
2016-08-18 10:03       ` Eric Wong
2016-08-15  6:16     ` Christian Couder
2016-08-15 18:08   ` Jakub Narębski
2016-08-15 18:25     ` Jakub Narębski
2016-08-16  9:30     ` Eric Wong
2016-08-16  9:34       ` Josh Triplett
2016-08-16 21:27         ` Eric Wong
2016-08-16 22:32           ` Josh Triplett
2016-09-07  1:08             ` Eric Wong
2016-08-16 12:27     ` Christian Couder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAP8UFD2mfa2hNDknEt=bsbXVn4xSSiyVYz94KL_JPbD66QrfPg@mail.gmail.com' \
    --to=christian.couder@gmail.com \
    --cc=durden@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j6t@kdbg.org \
    --cc=jnareb@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=larsxschneider@gmail.com \
    --cc=mhagger@alum.mit.edu \
    --cc=normalperson@yhbt.net \
    --cc=pclouds@gmail.com \
    --cc=peff@peff.net \
    --cc=ramsay@ramsayjones.plus.com \
    --cc=remi.galan-alfonso@ensimag.grenoble-inp.fr \
    --cc=sbeller@google.com \
    --cc=tboegi@web.de \
    --cc=tfnico@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).