search for: d12345

I'm not sure if this is well known, but it helped me so I thought I'd share it with you. When committing to gitmonorepo, (with git llvm push) you need to have committed to your local repo first and so you need to have crafted your commit message from your the Phabricator revision. (e.g. D12345) Phabricator has the ability to give you this commit message it would have used, even if you do not use arc to perform the commit/land This small script (attached) uses arc, jq and sed (but it can be relatively easily changed to use curl instead of arc) You need to provide your own conduit api...

...bly won’t have time to implement 1. and 2. in the near future on my own, but maybe someone would be interested in helping out. I think that could improve the experience for new contributors substantially: * Create a new patch: `llvm-patch upload` * Apply a patch from a review: `llvm-patch apply D12345`. WDYT? Cheers, Florian

Hello Everyone, This is my first attempt to getting used with the submission process. Trying to get the "good practice" with the coding standard, tools, mailing lists... and already a few questions: - Is it possible to "link" 2 related entries in Phabricator ? one for LLVM and one for CFE ? what's the best way of posting 2 related or dependent patches ? - I'd

...ar future on my >> own, but maybe someone would be interested in helping out. >> >> I think that could improve the experience for new contributors >> substantially: >> * Create a new patch: `llvm-patch upload` >> * Apply a patch from a review: `llvm-patch apply D12345`. >> >> WDYT? >> >> Cheers, >> Florian >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org >> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >> > ___________________...

...the near future on my > own, but maybe someone would be interested in helping out. > > > > I think that could improve the experience for new contributors > substantially: > > * Create a new patch: `llvm-patch upload` > > * Apply a patch from a review: `llvm-patch apply D12345`. > > > > WDYT? > > > > Cheers, > > Florian > > _______________________________________________ > > LLVM Developers mailing list > > llvm-dev at lists.llvm.org > > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > > ______________...

...is cumbersome and error prone (to me particularly, I make many mistakes). > What do you mean by "with mention" and what do you mean by "related" (I guess you man "not dependent, but interesting to consider together") When you write a ticket number, either in phab (D12345) or GitHub (#123), the UI creates a link to the mentioned issue/review. In Github, if you say things like "fixes #123", it closes automatically (which is not necessarily right, like "partially fixes #123" :). > My understanding from other people's comments (I've not...

On Tue, Oct 8, 2019 at 2:13 PM Nicolai Hähnle via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > I wonder if mailing list archives could (or perhaps already do) expose > an API that would allow importing past history into an e-mail > client-like viewer, or perhaps into an actual e-mail client. > I know that GNU mailing lists allow downloading MBOX files for their list

On Thu, 16 Jan 2020 at 18:45, David Blaikie <dblaikie at gmail.com> wrote: > I'm not sure where the idea that a patch series is anything other than that ^ came from. When I was talking about a patch series, it was/is with that definition in mind - ordered/dependent commits. I said "dependent series" to reinforce this idea that the kind of situation I was describing was one

OK, I've tried changing my printcap name from printcap to cups. Printing works fine locally using CUPS on the Samba box. What am I missing here? Why can't I print to the Samba box via the Windows and linux clients? Shared directories work fine. I am really frustrated here and have exhausted Google and all other resources I have. Here's my smb.conf for what it's worth.