On May 19, 2010, at 11:15 AM, Adam Barth wrote:
> Personally, I don't have multiple patches in my tree at the same time,
> so I don't understand what would be the most convenient for you.
> Removing the update step is easy, but I'm not sure how you would like
> to specify the changes to remove from the tree.
Good point. One of the many things I like about svn-unapply is the excellent
speed. It doesn’t have to look at the entire source tree, just unapply the
patch. I can imagine getting that same experience from unapply-from-attachment,
but it would be inconvenient to have to find and type in the bug number.
> We could add an "unapply-from-attachment" command, but that would
> involve fetching the patch from bugs.webkit.org again... Another
> option is that the upload command could store a copy of the patch
> locally that you could then use with svn-apply and svn-unapply
> directly.
To replicate my old workflow I’d need something that would keep local copies of
various patches I’m working on, or at least keep track of what they are so I
don’t have to remember patch or bug numbers.
Before I’d just make patches with svn-create-patch, give them names to help me
remember what I was doing, then apply and unapply them, revising as needed, and
attaching to bugs as needed.
The copies attached to the bugs also had the same descriptive names, so if I
downloaded them on another computer I could replicate the same good situation.
Again, I’m aware that git users have entirely different ways of accomplishing
the same thing and more.
It’s not obvious to me how to take a tool primarily designed for the git users
and make it great for me, although it seems tantalizingly close.
-- Darin
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
