You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Vaguely connected to #139 but I didn't want to hijack that issue.
With pwclient I do (for example) 'pwclient list msm' to list just patches w/ msm in the subject. It would be nice to be able to do similar. Although perhaps even better would be filtering on path (so you could just list the driver path(s) that you are interested in and see all the patches that touch the driver/subsystem/etc that you maintain.
The text was updated successfully, but these errors were encountered:
So the first part of the feature request was easy and is done.
The search by path touched is interesting, I'll leave the issue open for that part. We don't currently stored anything more than the whole text of the patch which doesn't map well with SQL and search in text blobs. The easier way to go about it would be to store more structured data about the patches (probably a number of 'Hunk' objects which would represent the diff hunks of the patch) and search through that data.
Definitely a direction I'd love to go towards to.
dlespiau
changed the title
Add filtering by subject and/or path in 'git-pw list'
Add filtering by file path in 'git-pw list'
Mar 3, 2016
ahh, cool.. I was hoping git already had some nice way to give you the changed paths (ie. similar to the --stat arg).. although I guess you want some way to get that from the server without having to download all the patches.
Vaguely connected to #139 but I didn't want to hijack that issue.
With pwclient I do (for example) 'pwclient list msm' to list just patches w/ msm in the subject. It would be nice to be able to do similar. Although perhaps even better would be filtering on path (so you could just list the driver path(s) that you are interested in and see all the patches that touch the driver/subsystem/etc that you maintain.
The text was updated successfully, but these errors were encountered: