public inbox for patchutils-list@sourceware.org
 help / color / mirror / Atom feed
From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: patchutils-list@sourceware.org
Cc: Markus Elfring <elfring@users.sourceforge.net>
Subject: Re: Support for index data by splitdiff command
Date: Wed, 07 Oct 2009 03:57:00 -0000	[thread overview]
Message-ID: <1254887860.2321.54.camel@segulix> (raw)
In-Reply-To: <1254885773.10925.ezmlm@sourceware.org>

[-- Attachment #1: Type: text/plain, Size: 2219 bytes --]

Hi sorry for the SPAM , my fault , elmz is too ... , last try ( I promise :)) 

Hi, 
Don't know if it help, I use svn and I use filterdiff.
filterdiff cleans all things that don't belongs to patch and that
includes Index ...
If you just want a clean splitdiff, you may use : 

svn diff | filterdiff  > txt; splitdiff -a txt


On Wed, 2009-10-07 at 03:22 +0000, patchutils-list-help@sourceware.org
wrote:
>         Hello,
>         
>         I would like to point out an open issue for the tool
>         "splitdiff" from the software package "patchutils 0.3.0-1.52".
>         
>         A special header "Index:" is mentioned in the article
>         "http://en.wikipedia.org/wiki/Diff". Tools like Subversion
>         write it into difference files. The current command does not
>         handle this data correctly.
>         
>         The following input ...
>         
>         Index: abc.h
>         ===================================================================
>         --- abc.h       (Revision 123)
>         +++ abc.h       (work copy)
>         @@ -1,1 +1,1 @@
>         -check
>         +out
>         Index: xyz.h
>         ===================================================================
>         --- xyz.h       (Revision 987)
>         +++ xyz.h       (work copy)
>         @@ -1,1 +1,1 @@
>         -test
>         +this
>         
>         ... is converted into the following arrangement by "splitdiff
>         -a".
>         
>         First source file:
>         --- abc.h       (Revision 123)
>         +++ abc.h       (work copy)
>         @@ -1,1 +1,1 @@
>         -check
>         +out
>         Index: xyz.h
>         ===================================================================
>         
>         Second source file:
>         --- xyz.h       (Revision 987)
>         +++ xyz.h       (work copy)
>         @@ -1,1 +1,1 @@
>         -test
>         +this
>         
>         
>         I would appreciate if the first file will keep its own header
>         and will not additionally get informations from the second
>         file.
>         
>         Regards,
>         Markus
-- 
Sérgio M. B.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2192 bytes --]

       reply	other threads:[~2009-10-07  3:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1254885773.10925.ezmlm@sourceware.org>
2009-10-07  3:57 ` Sergio Monteiro Basto [this message]
2009-10-10 19:10 SF Markus Elfring
2009-10-12 22:27 ` Sergio Monteiro Basto
2010-11-26  3:02 ` 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=1254887860.2321.54.camel@segulix \
    --to=sergio@sergiomb.no-ip.org \
    --cc=elfring@users.sourceforge.net \
    --cc=patchutils-list@sourceware.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).