Alas, my original request about changing the default sort order to be by date doesn't seem to be satisfiable as Doug mentioned. I also searched around on Atlassian forums and JIRA tracker for the JIRA project itself, seems like an issue that isn't fixed yet.
Regarding patch names, I too agree with Allen that extension should be .txt. I do run into patches every now and then which aren't interpreted as text files, so there are people out there using browsers that don't properly set the content-type. Thanks, +Vinod On Sat, Sep 10, 2011 at 3:30 AM, Eli Collins <e...@cloudera.com> wrote: > I updated HowToContribute, it people like this prose I'll advertise > the change to *-dev. > > Thanks, > Eli > > On Fri, Sep 9, 2011 at 2:53 PM, Eli Collins <e...@cloudera.com> wrote: > > On Fri, Sep 9, 2011 at 1:15 PM, Aaron T. Myers <a...@cloudera.com> wrote: > >> On Fri, Sep 9, 2011 at 12:57 PM, Eli Collins <e...@cloudera.com> wrote: > >> > >>> Patches for a specific branch should be named: jira-xyz-branch.patch > >>> where "branch" may be abbreviated, eg hdfs-123-security.patch > >>> > >> > >> +1, if we ever hope to implement HADOOP-7435 [1], it will be necessary > to > >> standardize the branch-name-in-patch-name scheme. > >> > > > > Good point. One way to enforce this is for Jenkins to only run tests > > against patches that follow this naming scheme, and to put the actual > > branch name in the patch (where no branch means trunk). Ie > > xyz-123.patch will run against trunk, xyz-123-branchx.patch will run > > against branch x and all other patches will be ignored by Jenkins. > > Someone tedious eg for "branch-20-security" but means we dont have to > > maintain a mapping. > > > > Thanks, > > Eli > > > > > > > >> -- > >> Aaron T. Myers > >> Software Engineer, Cloudera > >> > >> [1] https://issues.apache.org/jira/browse/HADOOP-7435 > >> > > >
