git and commit path sorting was: commit path sorting for Git and guidelines

[Alexander van Loon]

I’ve tried testing it (one commit of Calligra and one commit of KDevelop are currently waiting for classification) but just 
including the project name with a forward slash doesn’t seem to work, not for KDevelop either. The entry for Cirkuit was to 
figure out if automatic sorting worked for Git too, it didn’t work either so I removed that, but in principle it would be useful 
because that project also gets frequent commits and falls in the Office category.

On Sunday 16 January 2011 15:51:54 Marco Krohn wrote:
> Hi all,
> 
> I am splitting my answer in three different emails (and change the
> subject accordingly) to not mix too many things...
> 
> 
> On Sun, Jan 16, 2011 at 3:04 PM, Alexander van Loon
> <a.vanloon at alexandervanloon.nl> wrote:
> > With the import of commits from Git going again, automatic commit path sorting doesn’t seem to be working for Git? Is it 
not
> > implemented yet?
> 
> I did not look at the Enzyme source code, but my impression is that
> commit path sorting does work. However, "tools/configuration/commit
> path sorting" does not include rules for e.g.,
> "Calligra/words-change_tracking-ganeshp". My understanding is that if
> we add "Calligra/ => Office" to the configuration the classification
> will work--I have added this filter for now.
> 
> BTW: there is also a filter for "cirkuit.git ==> Office" - is that one
> really useful?
> 
> 
> Have a nice day,
>   Marco
> _______________________________________________
> Digest mailing list
> Digest at kde.org
> https://mail.kde.org/mailman/listinfo/digest