Brian May schrieb: > Thomas Keller wrote: >> I'd do it "safely" without messing around with _MTN/revision and move >> the current changes aside to re-apply them later on: >> >> $ mtn diff > current_changes.txt >> $ mtn revert . >> $ mtn db kill_rev_locally dcfbf59823cf21e292b60ba8f8463f65ea383597 >> $ patch -p0 < current_changes.txt >> > Unfortunately it won't work if you have renamed files, for example.
Yeah, I know, I know. The same goes out for attributes. But as I said earlier, I really would like to have an mtn patch command, which would solve these issues. Still, the proposed workflow works reasonable well for small changes in existing files. Thomas. -- GPG-Key 0x160D1092 | [EMAIL PROTECTED] | http://thomaskeller.biz Please note that according to the EU law on data retention, information on every electronic information exchange might be retained for a period of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Monotone-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/monotone-devel
