On Wed, 19 Feb 2014 15:17:05 +0100 Boris Faure <bo...@fau.re> wrote: > On 14-02-19 14:03, Tom Hacohen wrote: > […] > > One of the things I'd love seeing in 1.10 that will make your life > > much easier is tagging changes in the commit log. So for example, > > having #fix/#feature in the commit log will indicate a fix and a > > feature respectively. I went with the hashtag, because that's what > > people are used to from the web world, however we can use whatever > > identifier we would like. It's good to have a unique identifier, > > because it's easier to grep. > > I like the idea, but using '#' as first character can be a pita with > git since it would strip lines starting with '#' after editing the > commit message.
Didn't we try this already, "tagging" commits with "feature:" or "bug:"? Putting another symbol in front of it wont make a lot of difference. -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world.
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
