Re: Serialized Changeset

On 28 May 2005 09:23:12 -0500, kfogel@collab.net said:
> Tez Kamihira <tez@kamihira.com> writes:
> > [...]
> > Extended 'patch' is certainly one of them, of course.
>
> I'm not talking about extending the patch program, just to be clear.
> I'm talking about making sure the SCS format is "compatible" with
> today's patch program, in the sense that patch will do as much as it
> can with an SCS file and silently ignore the stuff it can't handle
> (such as metadata).

Ah, I got it.

  http://scm.bluegate.org/

Now current "Revision" is 1.

Curiously enough, I can't manage this text by any specific SCM
systems, nor put my favourite "arch-tag:" anywhere.

Cheers,

       - Tez

--- scs-0.txt 2005-05-29 11:27:14.932118880 +0900
+++ scs-1.txt 2005-05-29 11:40:25.878876696 +0900
@@ -561,6 +561,9 @@
   by software development, because they basically manage text files
   only.

+ Today's wide spreaded 'patch' tools SHOULD calmly discard the
+ Extended Unidiff Unit regions. They SHOULD NOT be choked by those
+ areas.

 3.3. Binary Unit

@@ -582,6 +585,8 @@
      -AAECAwQF
      +AAECAwQFBg==

+ Today's wide spreaded 'patch' tools SHOULD calmly discard the
+ Binary Unit regions. They SHOULD NOT be choked by those areas.

                              4. Hunk

@@ -590,6 +595,10 @@
 format as well and that part is only for reviewing purpose. Rest of
 the sections are pure extensions by SCS.

+Today's wide spreaded 'patch' tools SHOULD calmly discard all of the
+Hunk's regions except Standard ones. They SHOULD NOT be choked by
+those areas.
+
 4.1. Standard Hunk

   Standard Hunk Header usually has the following format:

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun May 29 05:11:51 2005