Not sure, you would probably pull a new patch of the new trunk. And in
that case give it a new name.
But I think that you should ensure you patch is stable enough, before it
is commit.
In an other apache project (solr) I see that a new feature / big
bug-fixes are often debated and people submit 'improved' patches to jira
before they commit a 'stable' patch to svn. But I'm not sure how this is
done in the wicket community
Thijs
Martijn Vos schreef:
Thijs wrote:
If you attach a new patch with the same filename.
Jira will automatically deprecate your old patch.
But what if someone has already applied/commited my original patch?
mcv.