[PATCH]: Optional explanation for options

[John A Meinel]

Aaron Bentley wrote:
> Martin Pool wrote:
>
>>>On 20/09/05, John A Meinel <john at arbash-meinel.com> wrote:
>>>Another approach, which lifeless has advocated, is to transmit the
>>>actual changes as a binary blob attached to the message, and a
>>>human-readable diff just as a summary.  This has some strengths and
>>>weaknesses:
>
>
> I would like to have changeset files be a single file, not a procedure
> for adding attachments, because I would like it to be possible to store
> changesets as files, and manipulate them as such.

I also like the idea that changesets are a single file, which is mostly
human readable, and can be sent attached to an email (and possibly inline).

But putting a base64 encoded portion at the bottom could possibly be
okay too. But only if you were trying to shove non-human meaningful
stuff like revision ids and hashes in there. I don't think any patch
information should be in binary form.

John
=:->


>
> Sure, we can say "changesets are MIME messages", and treat those as the
> files, but MIME can get pretty complicated and has many variations,
> whereas the changeset format is fairly simple.
>
> Aaron
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 253 bytes
Desc: OpenPGP digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20050921/f9897e75/attachment.pgp