Home
last modified time | relevance | path

Searched refs:working (Results 1 – 25 of 593) sorted by relevance

12345678910>>...24

/openbsd-src/usr.bin/newsyslog/
H A Dnewsyslog.c476 struct conf_entry *working; in parse_file()
499 working = calloc(1, sizeof(*working)); in parse_file()
500 if (working == NULL) in parse_file()
505 working->log = strdup(q); in parse_file()
506 if (working->log == NULL) in parse_file()
509 if ((working->logbase = strrchr(working->log, '/')) != NULL) in parse_file()
510 working->logbase++; in parse_file()
518 working in parse_file()
474 struct conf_entry *working; parse_file() local
[all...]
/openbsd-src/gnu/usr.bin/cvs/doc/
H A Dcvs.info-634 Local; run only in current working directory.
85 made within these working sources will be automatically added to a
102 Say you have been working on some extremely experimental software,
143 * Requires: working directory, repository.
148 The default action is to compare your working files with the revisions
180 Local; run only in current working directory.
187 present. With no `-r' option, the working file will be compared
189 will be compared to your current working file. With two `-r'
190 options those two revisions will be compared (and your working
326 Local; run only in current working directory.
[all …]
H A Dcvs.info-325 File: cvs.info, Node: Tags, Next: Tagging the working directory, Prev: Assigning revisions, Up:…
71 commands must be issued inside your working directory. That is, you
117 that release, but you cannot find the bug in the current working copy.
154 File: cvs.info, Node: Tagging the working directory, Next: Tagging by date/tag, Prev: Tags, Up:…
156 Specifying what to tag from the working directory
162 are checked out in the current working directory. For example, if the
163 copy of `backend.c' in working directory was checked out from revision
167 working directory and then runs `cvs commit' to transfer that
172 revisions, which may differ from locally modified files in your working
182 File: cvs.info, Node: Tagging by date/tag, Next: Modifying tags, Prev: Tagging the working direc…
[all …]
H A Dcvs.info-779 Make new working files read-only. See *Note Global options::.
96 Make new working files read-write. See *Note Global options::.
202 Local; run only in current working directory. *Note
239 Local; run only in current working directory. *Note
279 Local; run only in current working directory. See *Note
302 Diff revision for date against working file. See *Note diff
309 Local; run only in current working directory. See *Note
320 Diff revision for REV1 against working file. See *Note diff
335 Local; run only in current working directory. See *Note
345 Local; run only in current working directory. See *Note
[all …]
H A Dcvs.info-439 changes, and remove their working copies, before you take the
50 4. Tell everyone that they can check out again and continue working.
53 If someone had a working copy the CVS commands will cease to work
214 when users make changes in separate working directories (*note Multiple
229 working directories, see the discussion of reserved checkouts (file
275 this file, but it does not alter the working copy of the file that you
318 this model, developers can edit their own "working copy" of a file
322 then use CVS commands to bring their working copy up to date with the
393 revision' which is the revision that the file in the working directory
426 the repository and put in your working directory.
[all …]
H A Dcvs.texinfo222 @sc{cvs} also helps you if you are part of a group of people working
299 checked out working directories. If you write your
468 Suppose you are working on a simple compiler. The source
490 The first thing you must do is to get your own working copy of the
604 @cindex Removing your working copy
605 @cindex Releasing your working copy
607 Before you turn to other tasks you decide to remove your working copy of
633 also removes your working copy.
648 you how many modified files you have in your working
671 that you checked out with your working copy. When you see the output
[all …]
H A Dcvs.info-258 any other module. Use `cvs checkout CVSROOT' to get a working copy,
77 (once you have checked out a working directory) by simply allowing CVS
78 to use the repository that was used to check out the working directory
85 servers into your working directory. CVS will recurse and handle all
88 to set up a working directory:
95 The `cvs co' commands set up the working directory, and then the
116 which the developers will be working, you'll want disk space for
117 approximately one working directory for each developer (either the
163 the repository were made after the time of the backup, working
169 * Get a new working directory.
[all …]
/openbsd-src/usr.sbin/makefs/cd9660/
H A Diso9660_rrip.c203 int ca_used, susp_used, susp_used_pre_ce, working; in cd9660_susp_handle_continuation_common() local
207 working = 254 - space; in cd9660_susp_handle_continuation_common()
210 working -= node->su_tail_size + 4; in cd9660_susp_handle_continuation_common()
216 if (working < 0) in cd9660_susp_handle_continuation_common()
222 working -= CD9660_SUSP_ENTRY_SIZE(temp); in cd9660_susp_handle_continuation_common()
223 if (working >= 0) { in cd9660_susp_handle_continuation_common()
227 if (working >= 28) { in cd9660_susp_handle_continuation_common()
238 if (working <= 0) { in cd9660_susp_handle_continuation_common()
747 int working,len; in cd9660_rrip_add_NM() local
757 working = 1; in cd9660_rrip_add_NM()
[all …]
/openbsd-src/gnu/llvm/libcxx/docs/Status/
H A DCxx14.rst27 - LWG - Library working group
28 - SG1 - Study group #1 (Concurrency working group)
H A DCxx2b.rst25 - LWG - Library working group
26 - SG1 - Study group #1 (Concurrency working group)
H A DCxx17.rst26 - LWG - Library working group
27 - SG1 - Study group #1 (Concurrency working group)
H A DCxx20.rst26 - LWG - Library working group
27 - SG1 - Study group #1 (Concurrency working group)
/openbsd-src/gnu/usr.bin/cvs/
H A DFAQ106 Most development starts with everyone working on the same
154 - A CVS working directory satisfies the definition of "branch"
160 collection of files in your working directory. It is *not* the
195 Remember that you can think of your working directory as a "branch for
214 whole development organization working on the files.
216 Rather than trying to share a working directory, you can move onto a
218 the branch. Developers not working on the branch won't see your work
243 "Checkout" or "update" your working directory onto the branch.
253 Suggested procedure when using your working directory, which
254 contains the revisions of your working files you want to branch from:
[all …]
/openbsd-src/gnu/llvm/llvm/utils/vim/
H A DREADME10 an inspiration and starting point for those working on llvm c++ code.
16 If you find yourself working with LLVM Makefiles often, but you don't get syntax
/openbsd-src/gnu/llvm/llvm/utils/gn/
H A DTODO.txt9 - investigate feasibility of working `gn check`
24 - plugin() template with working rpath, exports thingers
/openbsd-src/gnu/llvm/lldb/docs/use/
H A Dremote.rst126 Note that the platform has a working directory of /tmp. This directory will be
146 Install and run in the platform working directory
149 To launch a locally built process on the remote system in the platform working
159 platform's current working directory only if the file has changed. The platform
166 Changing the platform working directory
169 You can change the platform working directory while connected to the platform
193 the platform's current working directory, we can set the platform file
203 instead of the platform current working directory. Only the main executable is
/openbsd-src/lib/libcrypto/x509/
H A Dx509_constraints.c326 char working[DOMAIN_PART_MAX_LEN + 1] = { 0 }; in x509_constraints_parse_mailbox() local
366 working[wi++] = c; in x509_constraints_parse_mailbox()
374 working[wi++] = c; in x509_constraints_parse_mailbox()
380 candidate_domain = strdup(working); in x509_constraints_parse_mailbox()
412 working[wi++] = c; in x509_constraints_parse_mailbox()
420 candidate_local = strdup(working); in x509_constraints_parse_mailbox()
423 memset(working, 0, sizeof(working)); in x509_constraints_parse_mailbox()
444 working[wi++] = c; in x509_constraints_parse_mailbox()
/openbsd-src/gnu/llvm/llvm/docs/
H A DBugLifeCycle.rst28 #. `Actively working on fixing`_
95 .. _Actively working on fixing:
97 Actively working on fixing bugs
100 Please remember to assign the bug to yourself if you're actively working on
101 fixing it and to unassign it when you're no longer actively working on it. You
/openbsd-src/gnu/usr.bin/cvs/src/
H A Dhistory.c224 static short working; variable
348 if (working)
414 working = 1;
565 if (working)
646 working = 0; /* User's workdir doesn't count here */
1529 if (working) in report_hrecs()
1586 (working && /* If must match "workdir" */
1600 if (working)
/openbsd-src/gnu/usr.bin/binutils/gas/
H A Dacinclude.m420 dnl working properly!
23 [AC_MSG_CHECKING([for working assert macro])
/openbsd-src/gnu/usr.bin/binutils-2.17/gas/
H A Dacinclude.m422 dnl working properly!
25 [AC_MSG_CHECKING([for working assert macro])
/openbsd-src/gnu/usr.bin/perl/cpan/Test-Simple/t/Legacy/
H A Duseing.t18 ok( !Foo->can('like'), 'import working properly' );
/openbsd-src/gnu/llvm/clang/www/
H A Dlibstdc++4.7-clang11.patch4 +++ include/std/type_traits (working copy)
/openbsd-src/gnu/usr.bin/perl/dist/Net-Ping/t/
H A D010_pingecho.t20 local $TODO = "Not working on os390 smoker; may be a permissions problem"
/openbsd-src/lib/libform/
H A Dfld_def.c308 New_Field->working = newpad(1, Buffer_Length(New_Field) + 1); in new_field()
393 (void)delwin(field->working); in free_field()

12345678910>>...24