[Sugar-devel] [RFC PATCH v0 0/8] Journal sorting by file size and creation time.

[Michael Stone]

On Thu, May 06, 2010 at 05:14:44AM +0000, Aleksey Lim wrote:
>On Sat, May 01, 2010 at 04:33:48PM -0300, Andrés Ambrois wrote:
>> This patchset implements sorting in the Journal UI as described in [0]. 
>> 
>> This feature was requested in [1] and sponsored by Activity Central [2].
>> 
>> Sorting by filesize is vital in the field where users need to free up disk
>> space. Currently, the only way to find candidates for deletion is to access
>> the expanded view of each entry, one by one. This can be a very time consuming
>> process and often leads to indiscriminate deletion and thus potential loss of
>> valuable data. This is bad.
>> 
>> Sorting by creation time (ctime) is also implemented as described in the Design
>> Proposal.
>> 
>> This implementation currently lacks two aspects which I hope will be sorted out
>> in the review process:
>> 
>> 1- The proposal does not include a specification for changing the order of the
>> sort. This patch assumes an ascending order.
>> 
>> 2- There are no icons for the sorting criteria. Or at least I couldn't find the
>> ones presented in the proposal. I'm sure someone from the design team could
>> vectorize the ones there.
>> 
>> v0: Initial submission to sugar-devel
>
>As current datastore and journal maintainer, some points:
>
>I'm still not sure will ml path proposal scheme work on not, it removes
>some bugs.sl.o issues but adds new e.g. it is pretty hard to collaborate
>(in my mind) via ml history, in case of bugs.sl.o, someone can just
>share http link to complicated query. Other thing is that on bugs.sl.o
>it is easy to query tickets by keywords for example.
>
>And since having patches both on bugs.sl.o and ml is pretty useless and
>there is no regular way to attach "0.90 targeted" keyword to ml posts,

The man page for "git format-patch" from git 1.7.1 shows options like

   --subject-prefix
   --add-header

which can be used to tag patches for branches.

These options can also be configured in .gitconfig or .git/config like so:

   [format]
   headers = "Organization: git-foo\n"
   subjectprefix = CHANGE

(@Martin, Bernie: how would one configure branch-specific format settings?)

Finally, Trac-like querying capabilities can be easily regained via email
search tools like "notmuch".

Regards,

Michael