[Webkit-unassigned] [Bug 57242] webkit-patch should support a placeholder for the bug number

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon May 2 15:17:17 PDT 2011


https://bugs.webkit.org/show_bug.cgi?id=57242





--- Comment #8 from David Kilzer (ddkilzer) <ddkilzer at webkit.org>  2011-05-02 15:17:17 PST ---
(In reply to comment #7)
> My workflow is thus:
> 
> 1.  Write the patch.
> 2.  Run webkit-patch upload (which prompts me for the bug title, creates the bug, runs prepare-ChangeLog for me, then I write the changelog, and it uploads the patch for me).

I actually dislike having to write the ChangeLog before running webkit-patch.  I feel that I would write inferior ChangeLogs because I'm required to finish before I do any other tasks, and if I do exit early, I have to start all over again, which makes me sad.

The latter item is a show-stopper for me.  I want "offline" behavior for the "upload" command so I can write my ChangeLogs on my own time, and just use "upload" to, well, upload the patch.

It shouldn't be that hard to make webkit-patch know when you already have a ChangeLog for a commit or a patch, and just use it.  (I don't expect anyone to implement this for me; I just haven't had time to re-familiarize myself with webkit-patch and Python recently.)

> 3.  Commit to my branch.
> <write my next patch>
> 
> I often just reset --hard after I've uploaded my patch and use webkit-patch apply-attachment to pull it back down (more of an svn/quilt workflow than a git one).  I find that if I make a new branch to start new work I will very often forget my branch that I just uploaded from and have trouble cleaning up branches some months later. :)  I commonly have some 50 branchs across my two Git checkouts (on two machines) than I have to wade through to find which patches actually landed vs. didn't. :)

I rename my branches to start with "bug-NNNNN-" to solve this.  Maybe webkit-patch should do that, too!  ;)

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list