git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tobias Klauser <tklauser@distanz.ch>
To: Junio C Hamano <gitster@pobox.com>,
	Christian Couder <chriscool@tuxfamily.org>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
	Eric Sunshine <sunshine@sunshineco.com>,
	git@vger.kernel.org
Subject: [PATCH 0/2] Add in-place editing support to git interpret-trailers
Date: Mon, 11 Jan 2016 14:33:31 +0100	[thread overview]
Message-ID: <1452519213-1819-1-git-send-email-tklauser@distanz.ch> (raw)

This patch series adds support for in-place editing to git interpret-trailers
akin to sed -i, perl -i.

v1->v2:
 - Split patch to make review easier, as suggested by Matthieu Moy.
 - Rename FILE * function parameters to a more readable name, as suggested by
   Matthieu Moy.
 - Write output to temporary file and rename after successfully written in full
   to avoid losing the original file in case of an error/interrupt. Pointed out
   by Eric Sunshine.

Tobias Klauser (2):
  trailer: use fprintf instead of printf
  interpret-trailers: add option for in-place editing

 Documentation/git-interpret-trailers.txt | 24 +++++++++++-
 builtin/interpret-trailers.c             | 13 +++++--
 t/t7513-interpret-trailers.sh            | 32 ++++++++++++++++
 trailer.c                                | 63 +++++++++++++++++++++++++-------
 trailer.h                                |  3 +-
 5 files changed, 115 insertions(+), 20 deletions(-)

-- 
2.7.0.1.g5e091f5

             reply	other threads:[~2016-01-11 13:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-11 13:33 Tobias Klauser [this message]
2016-01-11 13:33 ` [PATCH 1/2] trailer: use fprintf instead of printf Tobias Klauser
2016-01-11 13:33 ` [PATCH 2/2] interpret-trailers: add option for in-place editing Tobias Klauser
2016-01-11 16:33   ` Matthieu Moy
2016-01-11 17:13     ` Tobias Klauser
2016-01-11 17:24       ` Matthieu Moy

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=1452519213-1819-1-git-send-email-tklauser@distanz.ch \
    --to=tklauser@distanz.ch \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=sunshine@sunshineco.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).