From: Jonathan Nieder <jrnieder@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Git List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>,
Christian Couder <chriscool@tuxfamily.org>,
Daniel Barkalow <barkalow@iabervon.org>,
Jeff King <peff@peff.net>
Subject: Re: [RFC/ PATCH] revert: Allow arbitrary sequencer instructions
Date: Tue, 2 Aug 2011 22:53:53 +0200 [thread overview]
Message-ID: <20110802205353.GF2743@elie> (raw)
In-Reply-To: <1312260884-5087-2-git-send-email-artagnon@gmail.com>
Ramkumar Ramachandra wrote:
> Allow arbitrary sequencer instructions in the instruction sheet.
"So now I can ..." wait, what does this allow me to do? Your audience
hasn't read the patch yet.
> --- a/sequencer.h
> +++ b/sequencer.h
> @@ -32,6 +32,16 @@ struct replay_opts {
> size_t xopts_nr, xopts_alloc;
> };
>
> +struct replay_insn {
> + struct commit *commit;
> + enum replay_action action;
> +};
> +
> +struct replay_insn_list {
> + struct replay_insn *item;
> + struct replay_insn_list *next;
> +};
Ah, so this allows sequences like
revert A
pick B
pick C
revert D
Nit: why isn't the list-item struct something like
struct replay_insn item;
struct replay_insn_list *next;
which would save a little memory management and memory access
overhead (or even
enum replay_action action;
struct commit *operand;
struct replay_insn_list *next;
since every "struct replay_insn" exists in the context of an
insn list afaict)?
Anyway, the general idea seems good.
next prev parent reply other threads:[~2011-08-02 20:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 4:54 [GSoC update] Iterating over a stable series Ramkumar Ramachandra
2011-08-02 4:54 ` [RFC/ PATCH] revert: Allow arbitrary sequencer instructions Ramkumar Ramachandra
2011-08-02 7:52 ` Christian Couder
2011-08-02 20:53 ` Jonathan Nieder [this message]
2011-08-03 1:32 ` Ramkumar Ramachandra
2011-08-02 5:01 ` [GSoC update] Iterating over a stable series Ramkumar Ramachandra
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=20110802205353.GF2743@elie \
--to=jrnieder@gmail.com \
--cc=artagnon@gmail.com \
--cc=barkalow@iabervon.org \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.