Home
last modified time | relevance | path

Searched refs:committed (Results 1 – 25 of 62) sorted by relevance

123

/openbsd/src/usr.sbin/nsd/
Dxfr-inspect.c96 uint8_t committed; in inspect_header() local
110 if(!xi_diff_read_8(in, &committed) || in inspect_header()
128 printf("committed: %d (%s)\n", (int)committed, in inspect_header()
129 committed?"yes":"no"); in inspect_header()
345 uint8_t committed; in list_header() local
359 if(!xi_diff_read_8(in, &committed) || in list_header()
377 printf("; committed: %d (%s)\n", (int)committed, in list_header()
378 committed?"yes":"no"); in list_header()
Ddifffile.c1289 uint8_t committed; in apply_ixfr_for_zone() local
1309 if(!diff_read_8(in, &committed) || in apply_ixfr_for_zone()
1329 switch(committed) { in apply_ixfr_for_zone()
1392 zone->is_checked = (committed == DIFF_VERIFIED); in apply_ixfr_for_zone()
/openbsd/src/gnu/llvm/llvm/docs/
DCodeReview.rst23 are committed to the repository.
28 Code can be reviewed either before it is committed or after. We expect
29 significant patches to be reviewed before being committed. Smaller patches
32 be committed prior to an explicit review. In situations where there is any
33 uncertainty, a patch should be reviewed prior to being committed.
69 something after code has been committed about which you would have commented
74 original change was committed, it may be better to create a new patch to
102 ready to be committed. Specifically, once a patch is sent out for review, it
103 needs an explicit approval before it is committed. Do not assume silent
137 A patch is approved to be committed when a reviewer accepts it, and this is
[all …]
DDeveloperPolicy.rst140 * After the change has been committed to the repository, the potentially
165 committed are reviewed after they go in: you don't want everyone to assume
177 patches that are committed are actually reviewed.
243 committed to the main development branch are:
344 * If the commit is a bug fix on top of another recently committed patch, or a
455 For external tracking purposes, committed changes are automatically reflected
483 reviewed after they are committed.
489 after they are committed, depending on the nature of the change). You are
541 changes increases the odds that any of the work will be committed to the main
567 "obvious" and can be committed without review. Once the new API is in place
[all …]
DMyFirstTypoFix.rst409 committed!
422 The review will be updated when the change is committed.
DContributing.rst108 Once that is done the change can be committed. If you do not have commit
DHowToAddABuilder.rst62 will get feedback sooner after changes get committed.
/openbsd/src/gnu/usr.bin/perl/Porting/
Dsync-with-cpan880 my $committed;
887 or $committed = 1; # note system returns true for an error!
909 if ($committed) {
/openbsd/src/usr.sbin/unbound/doc/
DREADME.svn5 committed to the repository.
/openbsd/src/gnu/usr.bin/perl/win32/
Dwin32.c4799 static char *committed = NULL; /* XXX threadead */ variable
4822 if (committed && reserved && committed < reserved) in sbrk()
4825 addr = (char *) VirtualAlloc(committed,reserved-committed,MEM_COMMIT,PAGE_READWRITE); in sbrk()
4829 prev_committed = committed; in sbrk()
4830 committed = reserved; in sbrk()
4850 if (!committed) in sbrk()
4851 committed = base; in sbrk()
4853 brk = committed; in sbrk()
4864 reserved = base = committed = brk = NULL; in sbrk()
4875 if (brk > committed) in sbrk()
[all …]
/openbsd/src/sys/dev/pci/drm/i915/display/
Dintel_cx0_phy.c261 int lane, u16 addr, u8 data, bool committed) in __intel_cx0_write_once() argument
280 (committed ? XELPDP_PORT_M2P_COMMAND_WRITE_COMMITTED : in __intel_cx0_write_once()
294 if (committed) { in __intel_cx0_write_once()
319 int lane, u16 addr, u8 data, bool committed) in __intel_cx0_write() argument
329 status = __intel_cx0_write_once(encoder, lane, addr, data, committed); in __intel_cx0_write()
340 u8 lane_mask, u16 addr, u8 data, bool committed) in intel_cx0_write() argument
345 __intel_cx0_write(encoder, lane, addr, data, committed); in intel_cx0_write()
381 int lane, u16 addr, u8 clear, u8 set, bool committed) in __intel_cx0_rmw() argument
389 __intel_cx0_write(encoder, lane, addr, val, committed); in __intel_cx0_rmw()
393 u8 lane_mask, u16 addr, u8 clear, u8 set, bool committed) in intel_cx0_rmw() argument
[all …]
/openbsd/src/gnu/usr.bin/cvs/contrib/
Dintro.doc62 by you and not yet committed (preceded by an M). You will be
85 will not be committed to the central copy unless you do a 'cvs add'.
/openbsd/src/gnu/usr.bin/cvs/src/
Doptions.h.in130 * who committed the change. If you are committing the change logged
134 * As such, by default, CVS disallows changes to be committed by users
/openbsd/src/gnu/usr.bin/cvs/
DFAQ1029 merges committed changes from the Repository into the working file.
1063 branch greater than 1.1 (one you committed there), just throw the
2069 at a time. Directories don't need to be committed.
2861 new revision added by CVS, discarding work committed earlier by CVS
2873 8. I "updated" a file my friend, "bubba", committed yesterday. Why doesn't
2880 Example: You committed a source file at 5PM. Bubba updated his copy of
2881 the file, grabbing your changes, then changed and committed a new
2890 committed by someone else or because you deleted your working file,
2942 provide the same information (for files that are not being committed)
3142 committed within that directory.
[all …]
/openbsd/src/gnu/usr.bin/perl/pod/
Dperlgit.pod111 Changes to be committed:
117 (use "git add <file>..." to update what will be committed)
124 (use "git add <file>..." to include in what will be committed)
180 Changes to be committed:
235 (use "git add <file>..." to include in what will be committed)
724 work is committed against the current position of blead, so that you can
778 I<committed>. The commit is then actually performed when you run the
/openbsd/src/usr.sbin/nsd/doc/
DNSD-VERIFY-MODS45 In order to break this situation the committed field of each transfer is
53 updates which committed field is neither DIFF_CORRUPT or DIFF_INCONSISTENT).
/openbsd/src/gnu/gcc/gcc/config/cris/
Dpredicates.md83 ; or <URL:http://gcc.gnu.org/ml/gcc-patches/2005-10/msg00940.html> is committed.
/openbsd/src/gnu/usr.bin/cvs/doc/
Dcvs.info-488 revision which has been committed, use the `cvs log' command (*note
358 You have edited the file, and not yet committed your changes.
361 You have added the file with `add', and not yet committed your
365 You have removed the file with `remove', and not yet committed
369 Someone else has committed a newer revision to the repository.
379 Someone else has committed a newer revision to the repository, and
434 editing it. In the meantime someone else committed revision 1.5, and
740 Another user has committed changes to a file.
1305 revision. When a local modification is committed it is placed on the
Dcvs.info-7275 Force the file to be committed; disables recursion. See
399 Report on committed (modified) files. See *Note history
409 Last modified (committed or modified report). See *Note
986 committed. PROG runs with a single argument, the full pathname of
1098 program whenever files are committed (*note modules::). The files
1100 programs whenever something is committed.
1170 ready to be committed. This could be used, for instance, to verify
Dcvs.info-6271 All local modifications that have not yet been committed will be
996 has not yet been committed to the repository. If you delete your
1002 not yet committed the removal. *Note commit::.
1188 committed.
1194 needs to be committed.
Dcvs.texinfo629 committed. If history logging is enabled it also makes a note in the
951 who committed the revision. The history files are
3283 files to be committed even if they are not modified.
4134 committed on the branch. Be very careful so that you
4470 this must be done after the merge has been committed or the merge itself
4492 committed and check it out again.
4665 the file is committed. The @code{log} command displays
4953 When @var{new} is committed its revision numbers will
5061 options}) flag when @var{new} is committed its revision
5203 specified for every revision which has been committed,
[all …]
Dcvs.info-3619 It only works if at least one revision is already committed on the
1009 inside the repository when the file is committed. The `log'
1184 When NEW is committed its revision numbers will start again, usually
/openbsd/src/sys/nfs/
Dnfs_vnops.c1267 int committed = NFSV3WRITE_FILESYNC; in nfs_writerpc() local
1348 if (committed == NFSV3WRITE_FILESYNC) in nfs_writerpc()
1349 committed = commit; in nfs_writerpc()
1350 else if (committed == NFSV3WRITE_DATASYNC && in nfs_writerpc()
1352 committed = commit; in nfs_writerpc()
1373 *iomode = committed; in nfs_writerpc()
/openbsd/src/gnu/usr.bin/binutils/ld/
DChangeLog17 * pe-dll.c: Revert changes accidentally committed 2004-03-08.
/openbsd/src/gnu/gcc/libgomp/
Dconfigure.ac295 # ??? 2006-01-24: Paulo committed to asking autoconf folk to document

123