3 ms·

Good points! > I'm fascinated by your use case because for my professional work I've never created or shared a patch. I do driver development, and often times

by exDM69 11y ago

Good points! > I'm fascinated by your use case because for my professional work I've never created or shared a patch. I do driver development, and often times we're debugging an issue where toggling some hardware (or software) "mode" can make an issue go away or appear. These are the patches we end up making and sharing with coworkers but never merging. We need to be able to do quick and dirty hacks but we can't be putting that kind of stuff anywhere near master branch. I'd say 4 out of 5 patches I write never get merged (and they're usually really short patches, the code itself wasn't of any measurable effort). Moving from SVN to Git (or darcs/hg in my case) was certainly a big move. But I guess if you were coming from diff/patch/email/shell script background (like kernel before bitkeeper), it was probably very intuitive :)

forrestthewoods 11y ago
You can shelve a changelist in P4. And any other user can unshelve it. I'm not sure how different that is from creating/sending patches? Especially if done from the cmdline. This has been a fun, educational HN thread. Thanks for sharing!
- exDM69 11y ago
  > You can shelve a changelist in P4. And any other user can unshelve it. I know, and we use this sometimes. It's just not as easy as pushing to a dev branch in Git creating a patch with "git am" and emailing/copy-pasting to a pastebin or whatever. Thanks for sharing your point of view and making a very civilized discussion from obviously differing opinions :)
  - forrestthewoods 11y ago
    I've never tried this. But it looks like if you run "p4 diff -du file" it creates a patch that could be pastebinned. https://www.perforce.com/perforce/r14.2/manuals/cmdref/p4_diff.html https://www.perforce.com/perforce/r14.2/manuals/cmdref/p4_di... Branching still sucks in P4. But if it improves your work flow at all I figured it's worth mentioning.

by exDM69 11y ago

forrestthewoods 11y ago

You can shelve a changelist in P4. And any other user can unshelve it. I'm not sure how different that is from creating/sending patches? Especially if done from the cmdline. This has been a fun, educational HN thread. Thanks for sharing!

exDM69 11y ago
> You can shelve a changelist in P4. And any other user can unshelve it. I know, and we use this sometimes. It's just not as easy as pushing to a dev branch in Git creating a patch with "git am" and emailing/copy-pasting to a pastebin or whatever. Thanks for sharing your point of view and making a very civilized discussion from obviously differing opinions :)
- forrestthewoods 11y ago
  I've never tried this. But it looks like if you run "p4 diff -du file" it creates a patch that could be pastebinned. https://www.perforce.com/perforce/r14.2/manuals/cmdref/p4_diff.html https://www.perforce.com/perforce/r14.2/manuals/cmdref/p4_di... Branching still sucks in P4. But if it improves your work flow at all I figured it's worth mentioning.