Searched refs:commits (Results 1 – 25 of 75) sorted by relevance
123
| /openbsd/src/gnu/llvm/clang/tools/clang-format/ |
| D | git-clang-format | 146 commits, files = interpret_args(opts.args, dash_dash, opts.commit)
147 if len(commits) > 1:
153 if len(commits) > 2:
154 die('at most two commits allowed; %d given' % len(commits))
155 changed_lines = compute_diff_and_extract_lines(commits, files, opts.staged)
180 if len(commits) > 1:
181 old_tree = commits[1]
252 commits = [default_commit]
254 commits = args
255 for commit in commits:
[all …]
|
| /openbsd/src/gnu/llvm/compiler-rt/www/ |
| D | menu.html.incl | 14 <a href="http://lists.llvm.org/mailman/listinfo/llvm-commits">llvm-commits</a>
|
| /openbsd/src/gnu/llvm/llvm/docs/ |
| D | DiscourseMigrationGuide.md | 120 <tr><td>All-commits</td><td>no migration at the moment</td></tr>
122 <tr><td>cfe-commits</td><td>no migration at the moment</td></tr>
129 <tr><td>flang-commits</td><td>no migration at the moment</td></tr>
132 <tr><td>libc-commits</td><td>no migration at the moment</td></tr>
136 <tr><td>libcxx-commits</td><td>no migration at the moment</td></tr>
138 <tr><td>lldb-commits</td><td>no migration at the moment</td></tr>
142 <tr><td>llvm-branch-commits</td><td>no migration at the moment</td></tr>
144 <tr><td>llvm-commits</td><td>no migration at the moment</td></tr>
148 <tr><td>Mlir-commits</td><td>no migration at the moment</td></tr>
149 <tr><td>Openmp-commits</td><td>no migration at the moment</td></tr>
[all …]
|
| D | MyFirstTypoFix.rst | 96 code.(Checking out anonymously is OK - pushing commits uses a different
323 https://github.com/llvm/llvm-project/commits/main.
339 As our change is fairly simple, we'll add the cfe-commits mailing list
341 review. (For changes outside clang, llvm-commits is the usual list. See
343 all the \*-commits mailing lists).
362 details. Your commit message is already there, so just add cfe-commits
372 cfe-commits list, and anyone else subscribed to these kinds of changes.
477 you need to be subscribed to the relevant commits list before landing
478 changes (e.g. llvm-commits@lists.llvm.org), as discussion often happens
488 - if you used multiple fine-grained commits locally, squash them into a
[all …]
|
| D | GitBisecting.rst | 11 has a mostly linear history, it has a few merge commits that added projects --
104 descend into all reachable commits. Ideally, we'd want to tell it to only
114 That way, the commits in ``mlir`` are never evaluated.
117 skips all commits on that branch. It takes 1.5 minutes to run on a fast
|
| D | Phabricator.rst | 13 While Phabricator is a useful tool for some, the relevant -commits mailing list
16 to respond to free-form comments in mail sent to the commits list.
26 to the relevant -commits mailing list. If you are not subscribed to the commit
87 propagating attribution on commits when someone else has to push it for you.
116 correctly, llvm-commits or cfe-commits will be subscribed automatically;
134 them to participate. Many people will see the email notification on cfe-commits
135 or llvm-commits, and if the subject line suggests the patch is something they
144 …scribed `here <https://moz-conduit.readthedocs.io/en/latest/arcanist-user.html#series-of-commits>`_
201 is based on git's rebasing. These steps assume that you have a series of commits that
206 git rebase -i HEAD~<number of commits you have written>
[all …]
|
| D | Contributing.rst | 93 (We used to allow patches on the llvm-commits mailing list, but the mailing lists
100 when creating a review and if you are using `llvm-commits`, add them to the CC of
128 <Phabricator.html#committing-a-change>`_ for Phabricator based commits or
143 # Check that the list of commits about to be pushed is correct.
148 LLVM currently has a linear-history policy, which means that merge commits are
160 you are about to push and ask confirmation if you push multiple commits at once.
|
| D | MarkdownQuickstartTemplate.md | 8 LLVM's docs" and turn that into useful documentation mailed to llvm-commits
13 then send the new document to llvm-commits for review.
26 llvm-commits for review.
|
| D | HowToAddABuilder.rst | 28 * Be able to keep up with new commits to the main branch, or at a minimum
174 In 2020, the monorepo had just under 35 thousand commits. This works
175 out to an average of 4 commits per hour. Already, we can see that a
177 useful. However, those commits are not uniformly distributed. They
179 of recent (Nov 2021) working days, we routinely see ~10 commits per
180 hour during peek times, with occasional spikes as high as ~15 commits
|
| D | GitHub.rst | 33 be created with the specified commits.
|
| D | DeveloperPolicy.rst | 32 `llvm-commits mailing list
33 <http://lists.llvm.org/mailman/listinfo/llvm-commits>`_ and engaging another
51 subscribe to the "commits" mailing list for the subproject you're interested in,
52 such as `llvm-commits
53 <http://lists.llvm.org/mailman/listinfo/llvm-commits>`_, `cfe-commits
54 <http://lists.llvm.org/mailman/listinfo/cfe-commits>`_, or `lldb-commits
55 <http://lists.llvm.org/mailman/listinfo/lldb-commits>`_. Reading the
56 "commits" list and paying attention to changes being made by others is a good
280 bots will directly email you if a group of commits that included yours caused a
322 * The title should be concise. Because all commits are emailed to the list with
[all …]
|
| /openbsd/src/gnu/llvm/llvm/utils/git/ |
| D | pre-push.py | 132 commits = git('rev-list', range).splitlines()
134 commits.reverse()
135 return commits
|
| D | github-automation.py | 278 def create_branch(self, commits:List[str]) -> bool:
289 print('cherry-picking', commits)
294 for c in commits:
|
| /openbsd/src/gnu/llvm/llvm/utils/ |
| D | revert_checker_test.py | 59 commits = [
84 self.assertEqual(commits, logs)
|
| /openbsd/src/gnu/llvm/llvm/docs/Proposals/ |
| D | GitHubMove.rst | 138 to mandate making merge commits illegal in our canonical Git repository.
141 policy. We must rely on the community to avoid pushing merge commits.
144 `status checks` requires commits to be explicitly allowed before the push can happen.
173 4. Update the buildbots to pick up updates and commits from the GitHub
176 5. Update Phabricator to pick up commits from the GitHub repository.
179 7. Instruct downstream integrators to pick up commits from the GitHub
540 Also, since the monorepo handles commits update across multiple projects, you're
589 # Pull in all the commits.
670 Some downstream users track the order commits were made to subprojects
688 commits in the order implied by submodule updates::
[all …]
|
| D | VariableNames.rst | 223 of large commits.
240 blame`` to identify prior, more interesting commits [GreeneGitBlame]_
245 can ignore or "look through" a given set of commits.
246 A ``.git-blame-ignore-revs`` file identifying the variable renaming commits
270 "look through" commits may impact how big a change can be made.
284 #. Refactor the starter project in two commits:
|
| /openbsd/src/gnu/llvm/clang/www/analyzer/ |
| D | menu.html.incl | 38 <li><a href="http://lists.llvm.org/mailman/listinfo/cfe-commits">cfe-commits</a></li>
|
| /openbsd/src/gnu/llvm/clang/www/ |
| D | menu.html.incl | 37 <a href="http://lists.llvm.org/mailman/listinfo/cfe-commits">cfe-commits List</a>
|
| /openbsd/src/gnu/usr.bin/perl/Porting/ |
| D | git-deltatool | 238 my @commits = $self->git->log($self->last_tag . "..HEAD");
239 $_ = Git::Wrapper::XLog->from_log($_, $self->git) for @commits;
242 @list = grep { ! $_->notes } @commits;
245 @list = grep { $self->note_status( $_ ) eq $type } @commits;
|
| /openbsd/src/gnu/llvm/libcxx/docs/ |
| D | index.rst | 210 `Phabricator <https://llvm.org/docs/Phabricator.html>`_. Please add `libcxx-commits` as a subscribe…
211 Also make sure you are subscribed to the `libcxx-commits mailing list`_.
223 * `libcxx-commits Mailing List <http://lists.llvm.org/mailman/listinfo/libcxx-commits>`_
|
| /openbsd/src/gnu/usr.bin/perl/ |
| D | Changes | 22 of Changes files that listed the individual commits that had gone into
35 prior to Changes5.005 were not simple lists of commits, so can't be
|
| /openbsd/src/gnu/usr.bin/binutils-2.17/binutils/ |
| D | BRANCHES | 11 for the branch (e.g., "no commits without permission of X or Y").
|
| /openbsd/src/gnu/usr.bin/perl/dist/Search-Dict/ |
| D | README.patching | 26 7. If all is well, push your commits to blead or send a patch to p5p if you do
|
| /openbsd/src/gnu/usr.bin/perl/dist/ExtUtils-CBuilder/ |
| D | README.patching | 26 7. If all is well, push your commits to blead or send a patch to p5p if you do
|
| /openbsd/src/gnu/usr.bin/perl/pod/ |
| D | perlgit.pod | 58 You can see recent commits:
323 If you want to cancel one or several commits, you can use C<git reset>.
424 commits identified by the bisection process. Sometimes, particularly
428 L<perlhack/Building perl at older commits>.
437 ... do local edits, commits etc ...
722 Simple, one-off commits pushed to the 'blead' branch should be simple
723 commits that apply cleanly. In other words, you should make sure your
746 You will see your commits being re-applied, and you will then be able to
750 For larger sets of commits that only make sense together, or that would
774 as a side branch, with all its commits merged into the mainstream blead
[all …]
|
123