git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org, Elijah Newren <newren@gmail.com>,
	Stefan Beller <sbeller@google.com>, Jeff King <peff@peff.net>
Subject: Re: [PATCH 1/8] Add basic Coccinelle transforms.
Date: Mon, 06 Jun 2016 19:54:12 -0700	[thread overview]
Message-ID: <xmqqfuspu2sr.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160607023144.GA72717@vauxhall.crustytoothpaste.net> (brian m. carlson's message of "Tue, 7 Jun 2016 02:31:44 +0000")

"brian m. carlson" <sandals@crustytoothpaste.net> writes:

> My goal here is simply to avoid needing to include this set of
> transformations in each commit message, which would tend to bloat it
> considerably.

Yeah, I understand that.  Philosophically this is similar to what we
traditionally keep in contrib/examples/, where it is not really part
of git-the-product but is still shipped to help git developers.

The resulting changes looked reasonably clean and thorough (the
latter is understandable as it is a tool's output ;-), and the input
language quite understandable.  This sounds like a fun process.

Thanks.

      reply	other threads:[~2016-06-07  2:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-07  0:57 [PATCH 1/8] Add basic Coccinelle transforms brian m. carlson
2016-06-07  0:57 ` [PATCH 2/8] Apply standard object_id Coccinelle transformations brian m. carlson
2016-06-07  0:57 ` [PATCH 3/8] Convert struct diff_filespec to struct object_id brian m. carlson
2016-06-07  0:57 ` [PATCH 4/8] Rename struct diff_filespec's sha1_valid member brian m. carlson
2016-06-07  6:21   ` Johannes Sixt
2016-06-07  6:23     ` Jeff King
2016-06-07 19:14       ` Junio C Hamano
2016-06-07 23:12         ` brian m. carlson
2016-06-07  0:57 ` [PATCH 5/8] merge-recursive: convert struct stage_data to use object_id brian m. carlson
2016-06-07  0:57 ` [PATCH 6/8] merge-recursive: convert struct merge_file_info to object_id brian m. carlson
2016-06-07  0:57 ` [PATCH 7/8] merge-recursive: convert leaf functions to use struct object_id brian m. carlson
2016-06-07  0:57 ` [PATCH 8/8] merge-recursive: convert merge_recursive_generic to object_id brian m. carlson
2016-06-07  2:28 ` [PATCH 1/8] Add basic Coccinelle transforms Junio C Hamano
2016-06-07  2:31   ` brian m. carlson
2016-06-07  2:54     ` Junio C Hamano [this message]

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

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=xmqqfuspu2sr.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=newren@gmail.com \
    --cc=peff@peff.net \
    --cc=sandals@crustytoothpaste.net \
    --cc=sbeller@google.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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).