public inbox for patchutils-list@sourceware.org
 help / color / mirror / Atom feed
From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
Cc: patchutils-list@sourceware.org
Subject: Re: Support for index data by splitdiff command
Date: Sat, 10 Oct 2009 19:10:00 -0000	[thread overview]
Message-ID: <1408366744@web.de> (raw)

> filterdiff cleans all things that don't belongs to patch and that
> includes Index ...

I would prefer to keep all informations intact. Is still any fine-tuning needed for the deletion of unwanted source lines?

The command "cvs diff -u" generates also this data together with the field "RCS file:" which will be lost, too. Would you like to consider such details as supported extensions for the patch data format?

Regards,
Markus

             reply	other threads:[~2009-10-10 19:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-10 19:10 SF Markus Elfring [this message]
2009-10-12 22:27 ` Sergio Monteiro Basto
2010-11-26  3:02 ` Sergio Monteiro Basto
     [not found] <1254885773.10925.ezmlm@sourceware.org>
2009-10-07  3:57 ` Sergio Monteiro Basto
  -- strict thread matches above, loose matches on Subject: below --
2009-09-30 17:11 SF Markus Elfring

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=1408366744@web.de \
    --to=elfring@users.sourceforge.net \
    --cc=patchutils-list@sourceware.org \
    --cc=sergio@sergiomb.no-ip.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).