gnu-arch-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnu-arch-users] Re: Linus Torvalds <address@hidden> Re: log-buf-len dyn


From: Bruce Stephens
Subject: [Gnu-arch-users] Re: Linus Torvalds <address@hidden> Re: log-buf-len dynamic
Date: Fri, 03 Oct 2003 17:46:30 +0100
User-agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3 (gnu/linux)

Andrea Arcangeli <address@hidden> writes:

[...]

> Yes, taglines would solve it too, but it would still be absolutely
> unreadable in the email. tla has a chance to send a "readable"
> patchset instead, much better than `diff` could ever do. And at the
> other end of the wire it can import the ascii readable metadata
> separately from the data when you merge the patchset you received by
> email. No data would be lost. The email would contain only human
> readable payload, and no tagline is needed.

Ah, I see what you mean.  Yes, if you rely on taglines then you might
end up with a patchfile which would have the file moves hidden (they'd
be unambiguous to an SCM, but not easy to see).

>> So yes, I agree.  This information is probably best in a file on its
>> own, and it's easy to come up with such a format---it's pretty much
>> what arch already uses (the ,,index files).  (Might need some
>> modification to cover file names with spaces in and other horrors.)
>
> the one he sends by email I think should be really indipendent from
> the current format of explicit tags, but it should be derived from
> it of course. It should be more like a "move foo.c foo2.c\nrm
> foo3.c\ntouch foo5.c\mkdir xxx\nrmdir zzz" etc..

Much like the patch format that BK can export to, in fact.  (In that,
file renames are encoded as a patch deleting the file, a patch
recreating the file with the new name, and at the beginning of the
patchfile there's structured text indicating that it's really a
rename.)

The Linux kernel is available as these patches:
<ftp://nl.linux.org/pub/linux/bk2patch/>.

[...]





reply via email to

[Prev in Thread] Current Thread [Next in Thread]