238
When sending patches by email (optionall) send each one as a separate
239
mail, with a sequence number [%03d/%03d] at the start of the Subject.
240
See mail from linus 2005-04-07.
242
http://linux.yyz.us/patch-format.html
244
http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt
250
reorder patches by cherry-picking them from a main development tree
251
before sending them on.
257
re-add should give the same id as before
239
* Fix up diffs for files without a trailing newline
243
* Directly import diffs! It seems a bit redundant to need to rescan
244
the directory to work out what files diff added/deleted/changed when
245
all the information is there in the diff in the first place.
246
Getting the exact behaviour for added/deleted subdirectories etc
249
At the very least we could run diffstat over the diff, or perhaps
250
read the status output from patch. Just knowing which files might
251
be modified would be enough to guide the add and commit.
253
Given this we might be able to import patches at 1/second or better.
added
removed
doc/random.txt
