I haven't tried rewriting Bazaar history yet, but if it is even remotely similar to Git, trying to change that message after it was already published will cause a huge mess (on the order of requiring everyone to wipe their checkouts and start fresh), which is totally not worth it from the cost-benefit perspective. Obviously it was a misplaced joke. I have already taken disciplinary action that involved sending Liam a Serious Cat meme, so I think we should look the other way and carry on.

Regards, Krzysztof

2015-07-13 23:21 GMT+02:00 Martin Owens <doctormo@...400...>:

On Mon, 2015-07-13 at 00:55 -0700, LucaDC wrote:

...

I suppose that the message for commit 14242 was not really intended to be that.

It's certainly interesting. And I think you're right that the message doesn't fit the diff, so it's probably erroneous.

Fixing it involves one of the launchpad admins changing the repository settings while an rewritten comment in that commit is forced back in. Then putting it back.

Martin,

---

Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

On Tue, 2015-07-14 at 09:53 +0200, Krzysztof Kosiński wrote:

(on the order of requiring everyone to wipe their checkouts and start fresh)

Not quite. in bzr you can do a push or pull with a force overwrite option set. It rewrites just those chunks/commits that differ... of course the longer it's left the more it's not worth it :-)

You're clearly a newbie in disciplinary Internet memes. Send him a tollestia meme the next time ;-)

Martin,