similar to: Delete Phabricator metadata tags before committing

Can we fix this in reviews.llvm.org's fork of phab? https://github.com/phacility/phabricator/blob/cac3dc4983c3671ba4ec841aac8efac10744a80c/src/applications/differential/conduit/DifferentialGetCommitMessageConduitAPIMethod.php Seems straightforward(-ish) to drop the relevant fields there, that way `arc land` automatically DTRT. Jon On Fri, Dec 27, 2019 at 11:30 PM Mehdi AMINI via llvm-dev

I also find the "Reviewed by" tag useful (as well as the review link), for the same reasons. In fact, I don't even use arcanist to push commits, so I do it all by hand, and only include the "Reviewed by" and "Differential Revision" tags. On Fri, 27 Dec 2019 at 20:55, David Blaikie via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I don't think

The limitation with the "Reviewed by" line is that if you just use `arc` it indicates who was added as reviewer on the revision, but not who approved it. Because of this, I am wary of relying on this line for anything. If you want to know who reviewed a change, better click on the Differential Revision link and go to the source of truth. -- Mehdi On Thu, Jan 2, 2020 at 10:44 AM

I'm sure I've seen many commits with both "Reviewed by:" and "Reviewers:" tags, which look to have been done with arc (though I can't be sure). How were those generated? On Sat, 4 Jan 2020 at 19:12, David Blaikie <dblaikie at gmail.com> wrote: > Yeah, I tend to prune it down myself - and if the list has only one name > on it, it's usually a pretty

Hi, I'm turning my wheels on this and keep coming around to the same wrong solution - please have a look and give a hand ... The premise is: a DF like so > loremIpsum <- "Lorem ipsum dolor sit amet, consectetur adipiscing elit. Quisque leo ipsum, ultricies scelerisque volutpat non, volutpat et nulla. Curabitur consequat ullamcorper tellus id imperdiet. Duis semper malesuada

I just realised I hadn't updated the version of PHP Markdown and Extra on the dingus as I pretended I did in my two announcements. It is now fixed: PHP Markdown 1.0.2b7 and PHP Markdown Extra 1.1b1 can now be tested on the dingus. <http://www.michelf.com/projects/php-markdown/dingus/> Sorry for any inconvenience. Michel Fortin michel.fortin@michelf.com http://www.michelf.com/

Hello all! I''m having a problem which is driving me insane. It''s probably related to the fact that I''m new to javascript.... :) Here''s the thing, I have a couple of effects which are all being put in the queue. Some of these effects have callbacks; e.g. "afterFinish". But the calback is being made directly instead of after the effect is done. The

Hi folks, I''ve working and playing with acts_as_ferret and follow this fantastic tutorial: http://www.railsenvy.com/2007/2/19/acts-as-ferret-tutorial When I try to implement the field storage tip, it crash. So, I try to make it via script/console: 1. I have a simple model called Articles: class Article < ActiveRecord::Base acts_as_ferret :fields =>

This is kind of odd. [scarolan at host:~]$ cat loremipsum.txt Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec quis ipsum sed elit laoreet malesuada. Quisque rhoncus dui vitae eros euismod fermentum sollicitudin sem scelerisque. Nulla facilisi. Maecenas mollis pulvinar euismod. Duis viverra pharetra turpis eget feugiat. Nulla facilisi. Nullam facilisis, felis vitae lacinia

I'm using omega for a sitesearch and currently having a problem trying to filter $field(sample). At the moment it returns text from the page header and navigation within the sample, ideally I'd like it to return only the page content. I've been trying various omegascript commands to trim the output or seperate the fields and also looking at scriptindex to control how the xhtml is

> On Feb 20, 2020, at 14:25, Johannes Doerfert <johannesdoerfert at gmail.com> wrote: > > On 02/20, Louis Dionne via llvm-dev wrote: >> I know there has been significant discussion about "moving" from >> Phabricator to GitHub reviews and pull requests, etc. I'm not >> suggesting that we do anything in terms of global LLVM policy. >> However, as

> On Mar 3, 2020, at 17:16, Shoaib Meenai <smeenai at fb.com> wrote: > > `arc patch` should preserve the author information in the original commit, if there was any. At least it has in my experience. Yes, but I think people can upload raw patches to Phabricator without using `arc diff`. I know I ran into one of these just last week where I used Johannes' script (thanks!) and

> On Mar 3, 2020, at 18:48, Eric Christopher <echristo at gmail.com> wrote: > > I'm one of those people ;) That's not something to be proud of if you expect a maintainer to commit on your behalf. If you commit yourself, then whatever. Louis > > -eric > > On Tue, Mar 3, 2020 at 2:20 PM Louis Dionne via llvm-dev <llvm-dev at lists.llvm.org

On 2020-04-30, Robinson, Paul via llvm-dev wrote: >For the tools (which I know is mostly what James works on) I’d say new command-line options are worth release-noting as a way to advertise their existence. > >From: llvm-dev <llvm-dev-bounces at lists.llvm.org> On Behalf Of David Blaikie via llvm-dev >Sent: Thursday, April 30, 2020 11:47 AM >To: James Henderson <jh7370.2008

Hello, I add a node Fedora 17. The reports are a aperture in puppet-server in /var/ lib/puppet/reports but not in Dashboard. While all other Fedra (16, 15, 14) are visible in Dashboard. Do you have an idea? Thank you. mauris -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit

Hi, I know there has been significant discussion about "moving" from Phabricator to GitHub reviews and pull requests, etc. I'm not suggesting that we do anything in terms of global LLVM policy. However, as a maintainer of libc++, I commit __a lot__ of other people's code for them. It would be a huge time saver for me if I could nicely suggest to contributors (not force them) to

Hi I'm trying to change a commit message that became malformed when pushing to trunk svn propedit svn:log --revprop -r 243434 > svn: E175002: DAV request failed; it's possible that the repository's > pre-revprop-change hook either failed or is non-existent > svn: E175002: Repository has not been enabled to accept revision > propchanges; > ask the administrator to

Eh - I'd say "Big" new features (hey, LLVM supports DWARFv5, or Split DWARF, or DWARF type units, or DWARF compression (though I don't think I wrote any release notes for several of those features that I implemented)). I wouldn't bother release noting changes in output format for tools we don't consider to have stable output, or changes in robustness/better error

On Tue, Jul 28, 2015 at 10:42 AM, Martell Malone <martellmalone at gmail.com> wrote: > Hi > > I'm trying to change a commit message that became malformed when pushing > to trunk > > svn propedit svn:log --revprop -r 243434 >> svn: E175002: DAV request failed; it's possible that the repository's >> pre-revprop-change hook either failed or is

2014-07-12 14:00 GMT+04:00 Richard W.M. Jones <rjones@redhat.com>: > It depends entirely on what the Linux kernel and tools can do. If > there are properly maintained Linux tools for resizing BSD slices, > then it should be no problem to add this. > > Compare with 'ntfsresize', where ntfs-3g exists and is well-maintained > and available in the majority of Linux