search for: _option_

...ollisions when different messages in the same page have the same inside link names (footnotes, title links). I guess similar issues are met on wiki implementations, so solutions adopted for wikis might be what I am looking for. Has this question already been met? May I suggest the addition of an _option_ to add a key to each link or link pair (`[^1]` and `[^1]: ...` for instance), that could help insulate each message from its neighbors? I could be done by defining a random 6-8-char key for each instance of PHP Markdown, and appending or prepending it to the name of each element in the html output...

I think we definitely will want to support github PRs, at the very least as an _option_, even if we continue running/preferring phabricator. Github PRs are how everyone who is not already super-involved in the llvm project is going to want to contribute changes, and we ought to be as welcoming as possible to such users. On Tue, Mar 19, 2019 at 3:15 PM Roman Lebedev via cfe-dev <...

...that it started uploading the file, but it didn't create it directly on the other side, but instead created some temporary file (.rx.gz.J4r4qe). I didn't quite like that and looked for an option which would turn this off, but didn't find out anything (it would be useful to have such an _option_, so that you have the file available when it's still being uploaded yet). I interrupted the running rsync so that I could test if it can't be accomplished in any way, but I was unsuccessful. As I used --preserve (part of -P), the temporary file was still there (but not renamed to the fin...

On Wed, 2014-03-05 at 13:18 -0500, Gene Cumm wrote: > Second, I notice the Altiris server specifies _3_ options of code 43, > including one of length 253. The pack/unpack _should_ handle this but > may split it differently. That's legal, and treated as if the values had been concatenated. See RFC2131, section 4.1, and particularly the second paragraph on page 24. Unfortunately, a

...appear only once, unless otherwise > specified in the options document." I don't see any indication of any > options that DO allow it unless "The information is an opaque object > of n octets" implies arbitrary length. What that text is trying to say is that a logical _option_ can appear only once, but that multiple TLV's can appear with the same tag, in which case they are concatenated together to obtain the length of the option. The only exception is if the specification for the option in question specifically says that the option can appear multiple times, which...

Hi, I would like to follow up on the previous thread[1], where there was a consensus to disallow merge commits in the llvm github repository, and start a discussion about how we should enforce this policy. Unfortunately, GitHub does not provide a convenient way to fully enforce this policy. We can enforce it for pull requests, but not for direct pushes to the master branch, so we will have to