reject patches based on what diff format they are in




16 years ago
9 years ago


(Reporter: John Vandenberg, Unassigned)


Dependency tree / graph



(2 attachments)



16 years ago
Context diffs are much harder to review, and mostly it is simpler to just
request the developer attach the patch in a different format.  Bugzilla can
enforce this process by rejecting the patch, giving the developer a nice message
describing how they can create a Unified patch.
This would be good for b.m.o, but would be useless for projects that use other
kinds of version management systems. I think it might be better to be able to
have a patch filter that can be written in perl and included in the bugzilla
dir. It could be made so this filter is easy to add. The filter would scan the
patch (In this case, make sure its the right type).

Comment 2

16 years ago
I have added the filter to my local copy of (see bug 115910), and added
a param to turn it off for sites which there is no parser for.  It should be
easy enough to add other formats as required for other sites.
Priority: -- → P4
Target Milestone: --- → Future

Comment 3

16 years ago
Created attachment 66628 [details] [diff] [review]
patch to use

Comment 4

16 years ago
Created attachment 66629 [details]

small with only sub Format

Comment 5

16 years ago
New on bug 115910.

Comment 6

15 years ago
This should be able to go into 2.18 as that is the release bug 115910 is
targetted for.
Assignee: justdave → zeroJ
Depends on: 115910
Target Milestone: Future → Bugzilla 2.18


15 years ago
Depends on: 174942

Comment 7

15 years ago
I am not sure if this is necessary anymore, if bug 174942 goes in.  With Patch
Viewer, we can transform a normal diff into a unified diff so that people who
want to view it in context or apply it will be able to do so easily.  It cannot,
however, add context for patches if a Bugzilla does not have a cvs repository,
so if that is the main reason these patches are easier to review, this will
still be useful.

For b.m.o, I think bug 174942 will be enough.

Comment 8

14 years ago
Patch Viewer is in the tree, and allows the user to turn any diff format (at
least any of the ones I found) into raw unified.  This is technically orthogonal
to the problem in this bug, however.  A few small changes could be made to
PatchIterator to make it report the type of diff it found, so that we don't have
two patch parsers, but in the end that particular point of code sharing probably
doesn't matter much.

Comment 9

14 years ago
Unloved bugs targetted for 2.18 but untouched since 9-15-2003 are being
retargeted to 2.20
If you plan to act on one immediately, go ahead and pull it back to 2.18.
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004.  Anything flagged
enhancement that hasn't already landed is being pushed out.  If this bug is
otherwise ready to land, we'll handle it on a case-by-case basis, please set the
blocking2.20 flag to '?' if you think it qualifies.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22


12 years ago
Assignee: jayvdb → administration
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Bugzilla 2.22 → ---


11 years ago
Depends on: 372974

Comment 11

11 years ago
There are times when a unified diff is not possible.  Rejecting a patch is terminal.  Warning the user and offering them an opportunity to confirm yes, really use a context diff is much more user-friendly.

Comment 12

9 years ago
Rejecting patches means Bugzilla should understand many different formats (git, CVS, bzr, ...) and make sure the format is incorrect (or rather: unwanted). That's not something I want upstream as it adds complexity for mostly no benefit.
Last Resolved: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.