- User Since
- Feb 10 2015, 6:19 PM (226 w, 5 d)
Nov 11 2016
Dec 7 2015
OK, to me those are 2 very different issues, T5000 is about having a workflow integrated into git and this one is just about allowing users to download the diffs submited to phab in the same exact same form as proposed instead of a stripped down version... I am not sure how you can say they are the same issues, but anyway, looks like there is no way we agree on that at that point (second time you close the issue, in one day...)
- This ticket basically boils down to "I/users don't like arc/phabricator", which is not a fun ticket to deal with. The actual need ("apply pending change locally") is already well-supported, in multiple ways, just not in the way you like.
I use git phab and am very happy with it, it uses arc in the background (at least for now).
To be able to know on what commit the patch was base and most importantly rebase it, you need to have the metadatas. What is your concern about adding that feature?
Oct 11 2015
Oct 9 2015
I am writing a git module to create revisions from git, it is quite similar to arc but I want to avoid rewriting commit messages (Summary and things like that), have a better integration with git and allow sending branches without squashing the commits.
Oct 8 2015
Oct 2 2015
I see, how could I set the Diff repository (can't find a way to do that in the UI) or actually get the revision repository from conduit?
Jul 10 2015
Feb 20 2015
I just managed to get it working specifying the base commit by hand.
I did update arcanist + libphutil (and by update I even mean removed the repos and cloned again) as recommanded on https://secure.phabricator.com/T7330 but that issue is still here:
Feb 19 2015
I did update libphutil locally, does not seem to have changed anything
I updated the serverm abd got latest libphutil
How could it possibly be due to the server as I have not even communicated with the server to me?
Feb 13 2015
Sounds good, thanks a lot for looking into that!
Feb 10 2015
We can probably make this a little more obvious in the UI and link the copy On Diff #1234 to the appropriate place.
Ok, so here is the workflow:
You can not *add* comments, but the problem I see is that you can not answer a comment, which is usefull on an already updated diff.