Jeff King writes:
> So if we are comfortable with saying that this is a new feature to have
> the machine-readable trailer version, and there isn't a robust way to
> get historical revert information (because there really isn't[1]), then
> I think we can just punt on any kind of trailer-normaliza
On Thu, Nov 08, 2018 at 09:36:56AM +0900, Junio C Hamano wrote:
> Duy Nguyen writes:
>
> > There is still one thing to settle. "revert -m1" could produce
> > something like this
> >
> > This reverts commit , reversing
> > changes made to .
>
> I do not think it is relevant, with or with
Duy Nguyen writes:
> There is still one thing to settle. "revert -m1" could produce
> something like this
>
> This reverts commit , reversing
> changes made to .
I do not think it is relevant, with or without multiple parents, to
even attempt to read this message.
The description is not
On Wed, Nov 07, 2018 at 04:30:38PM +0100, Duy Nguyen wrote:
> > Could we help the reading scripts by normalizing old and new output via
> > interpret-trailers, %(trailers), etc?
> >
> > I think "(cherry picked from ...)" is already considered a trailer by
> > the trailer code. If the caller instru
On Tue, Nov 6, 2018 at 11:11 PM Jeff King wrote:
>
> On Tue, Nov 06, 2018 at 06:48:22PM +0100, Ævar Arnfjörð Bjarmason wrote:
>
> > The implementation looks fine to me, but as noted in
> > https://public-inbox.org/git/8736se6qyc@evledraar.gmail.com/ I
> > wonder what the plausible end-game is.
Jeff King writes:
> Could we help the reading scripts by normalizing old and new output via
> interpret-trailers, %(trailers), etc?
>
> I think "(cherry picked from ...)" is already considered a trailer by
> the trailer code.
;-)
Great minds think alike, I guess. I think it is a great idea
t
Nguyễn Thái Ngọc Duy writes:
> OK here is a less constroversal attempt to add new trailers. Instead
> of changing the default behavior (which could be done incrementally
> later), this patch simply adds a new option --append-trailer to revert
> and cherry-pick.
I almost agree, except that the t
On Tue, Nov 06, 2018 at 05:11:18PM -0500, Jeff King wrote:
> On Tue, Nov 06, 2018 at 06:48:22PM +0100, Ævar Arnfjörð Bjarmason wrote:
>
> > The implementation looks fine to me, but as noted in
> > https://public-inbox.org/git/8736se6qyc@evledraar.gmail.com/ I
> > wonder what the plausible end
On Tue, Nov 06, 2018 at 06:48:22PM +0100, Ævar Arnfjörð Bjarmason wrote:
> The implementation looks fine to me, but as noted in
> https://public-inbox.org/git/8736se6qyc@evledraar.gmail.com/ I
> wonder what the plausible end-game is. That we'll turn this on by
> default in a few years, and the
On Tue, Nov 06 2018, Nguyễn Thái Ngọc Duy wrote:
> OK here is a less constroversal attempt to add new trailers. Instead
> of changing the default behavior (which could be done incrementally
> later), this patch simply adds a new option --append-trailer to revert
> and cherry-pick.
>
> Both will
OK here is a less constroversal attempt to add new trailers. Instead
of changing the default behavior (which could be done incrementally
later), this patch simply adds a new option --append-trailer to revert
and cherry-pick.
Both will show either
Reverts: [~]
or
Cherry-picked-from: [~]
11 matches
Mail list logo
