06-16-2004
I detest: FreeBSD 5.2.1 is not `unstable'. Granted it hasn't been tagged `stable', per se, as yet, but you make it sound worse than Microsoft Windows.
However, I do agree with your remark regarding a mission critical server. If this is what your purpose is, then use the `stable' branch, otherwise, use (as I do) the latest 5.x-RELEASE.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi
I want to write to my output_file using:
if((fptr = creat(output_file, _S_IWRITE)) == -1)
{
printf("output_file..."..);
return (1);
}
for(...)
{
_write(fptr, buffer, BUF_SIZE);
}
It says "_S_IWRITE" undeclared!!!
Anybody knows what function I can use for that and what I... (3 Replies)
Discussion started by: lacasa
3 Replies
2. UNIX for Dummies Questions & Answers
I am on AOL now,and i am using 56 k,i was gonna install FreeBSD,but i dont know if aol works on BSD,or my modem.
Do they work on BSD? (2 Replies)
Discussion started by: kita
2 Replies
3. UNIX for Dummies Questions & Answers
i am new at unix and am VERY confused about the compression processes. what progs do i need to unzip and zip files? there must be a standard one similar to winzip? (1 Reply)
Discussion started by: Mindscan
1 Replies
4. UNIX for Dummies Questions & Answers
What is FreeBSD, who does use Free? (3 Replies)
Discussion started by: cyberangel
3 Replies
5. BSD
B]I want the best of the best FreeBSD version for my study in Unix...please sugest me... Thanks (5 Replies)
Discussion started by: israel
5 Replies
6. BSD
I just download the FreeBSD 5.3 i386 iso files. And I have a problem now, I can't copy the 5.3-RELEASE-i386-disc2.iso to the cd, I try a lot of times, even change lots of blank cd to try but still cannot. But I can copy the other three iso files, i.e. 5.3-RELEASE-i386-bootonly.iso,... (4 Replies)
Discussion started by: GarbageKing
4 Replies
7. BSD
Hi to all,
Iam doing a project in Free BSD and i am stuck with a puzzle. Please any one of you clarify my doubt :
How to add a mechanism to check the status of the file system which alerts the root user via. email if any single partition is greater than 90% full. This alert should include the... (3 Replies)
Discussion started by: tadakamalla
3 Replies
8. Programming
Hello there,
My mulithreaded application (which is too large to represent the source code here) is crashing after installing FreeBSD 7.1-RELEASE/amd64.
It worked properly on others machines (Dual Cores with 4GB of RAM - FreeBSD 6.2-RELEASE/i386).
The current machine has 2x Core 2 Duo... (1 Reply)
Discussion started by: Seenquev
1 Replies
9. Fedora
I'm using Windows mostly and the only *nix thing I used during my life was cygwin (I like command line :)).
But currently I have (by an occasion) a DVD with latest FreeBSD. I don't know why, but I want to install it...
But probably, this OS is too difficult for a beginner. I heard, it's used on... (3 Replies)
Discussion started by: TeenageWerewolf
3 Replies
LEARN ABOUT OSX
git-patch-id
GIT-PATCH-ID(1) Git Manual GIT-PATCH-ID(1)
NAME
git-patch-id - Compute unique ID for a patch
SYNOPSIS
git patch-id [--stable | --unstable]
DESCRIPTION
Read a patch from the standard input and compute the patch ID for it.
A "patch ID" is nothing but a sum of SHA-1 of the file diffs associated with a patch, with whitespace and line numbers ignored. As such,
it's "reasonably stable", but at the same time also reasonably unique, i.e., two patches that have the same "patch ID" are almost
guaranteed to be the same thing.
IOW, you can use this thing to look for likely duplicate commits.
When dealing with git diff-tree output, it takes advantage of the fact that the patch is prefixed with the object name of the commit, and
outputs two 40-byte hexadecimal strings. The first string is the patch ID, and the second string is the commit ID. This can be used to make
a mapping from patch ID to commit ID.
OPTIONS
--stable
Use a "stable" sum of hashes as the patch ID. With this option:
o Reordering file diffs that make up a patch does not affect the ID. In particular, two patches produced by comparing the same two
trees with two different settings for "-O<orderfile>" result in the same patch ID signature, thereby allowing the computed result
to be used as a key to index some meta-information about the change between the two trees;
o Result is different from the value produced by git 1.9 and older or produced when an "unstable" hash (see --unstable below) is
configured - even when used on a diff output taken without any use of "-O<orderfile>", thereby making existing databases storing
such "unstable" or historical patch-ids unusable.
This is the default if patchid.stable is set to true.
--unstable
Use an "unstable" hash as the patch ID. With this option, the result produced is compatible with the patch-id value produced by git 1.9
and older. Users with pre-existing databases storing patch-ids produced by git 1.9 and older (who do not deal with reordered patches)
may want to use this option.
This is the default.
GIT
Part of the git(1) suite
Git 2.17.1 10/05/2018 GIT-PATCH-ID(1)