| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
be primarily working on Alpha ports.
By the way, he has been the only postmaster in the history of jp.freebsd.org.
|
| |
|
|
|
|
| |
machines) to the list of committers. Welcome, Dirk!
|
|
|
|
| |
purpose unknown).
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Kenji Sada <sada@email-ne.jp>
Seiichirou Hiraoka <flathill@flathill.gr.jp>
to the rank of committers. They are planning to make the ports/japanese
category even less manageable. Welcome aboard!
|
| |
|
|
|
|
|
| |
Bill will also stop El Nino (if he has time after the ports). Welcome,
Bill!
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Now I just need to figure out how Robert managed to commit the CFS
stuff without being in here. :-)
|
|
|
|
|
|
| |
Motoyuki Konno <motoyuki>
to the starship. Welcome aboard!
|
| |
|
|
|
|
|
|
| |
part of the standard distribution.
Welcome, Andrzej!
|
|
|
|
|
| |
As is traditional, you should move your entries in the handbook from
the contributors section to the committers section as your first action.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
among other things, fix the ORBacus port. Oh, and please don't forget
to move yourself from the additional contributors section to the
developers section in the handbook.
|
| |
|
| |
|
|
|
|
| |
This is a workaround until the postmaster fix his scripts.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
He has brought this on himself by blanket-bombing me with patches which
close PRs, now he can do it himself! :-)
I pressume the ritual instructions will be forwarded shortly.
Your very first duty is to add yourself to the rooster in the handbook.
Welcome!
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
("mph") to our esteemed (and overworked) rank of ports committers.
Welcome aboard, flight officer Hunt. It's too early in the morning
for me to type in the welcome message, so please go dig up the one I
sent to flight officer Kuriyama yesterday. Everything in there
applies to you too (including the parts of finally being able to work
on your own PRs).
Lieutenant Asami signing off. (It's going to be a long day....)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Everyone please join me in welcoming aboard Mr. Jun Kuriyama
("kuriyama") to the spaceship. He will be handling the docking
setups (aka ports).
If I haven't screwed up anything (which I probably have, but that is
not a certainty until you actually run into one of them), you should
have everything enabled so you can check out and commit to the tree by
now. Change your forwarding address on hub's /var/forward/kuriyama if
you wish, I set up to your default address. In addition to freefall
(the commit machine), you have accounts on hub (aka the mail hub),
catfish (the -stable test building box) and bento (the -current test
building box, aka Satoshi's lunchbox). Don't ask me why your
password file is duplicated on all four machines. I use ssh so I
never type my password anyway.
Your first assignment is to update the ship's roster in the handbook.
In particular, you are a "FreeBSD Developer" now! (Yeah, like you
weren't before.) If/when you do that task successfully, you are
allowed to look at the GNATs database and start committing ports from
there. (Yes, finally someone is closing your PR's!)
Have a nice tirp. Starship Mate Satoshi signing off.
|
|
|
|
|
| |
Peter! Erm. I think that's enough committers for right now though - we're
growing too fast, ack! :)
|
| |
|
| |
|
|
|
|
| |
some unidentifyable 8 bit char :)
|
| |
|
| |
|
| |
|
|
|
|
| |
Reviewed by: jdp, core (a few weeks ago)
|
|
|
|
| |
his tx driver directly. He's familiar with CVS.
|
| |
|
|
|
|
| |
any issues that might come up.
|
| |
|
| |
|
|
|
|
| |
for being honest and telling us so.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
(jseger) has joined the list of the distinguished committers.
If I haven't screwed up something, you should be able to commit now,
Justin. Please move yourself to the committers section in the
handbook (the usual first assignment :).
|
| |
|
|
|
|
|
| |
commit, as opposed to see the same boring non-information only all the time.
Also mention the purpose of the `PR' line.
|
|
|
|
| |
for the first 6 months.
|
| |
|
| |
|
|
|
|
| |
Well, he promised us to compete with Philippe Charnier :), let's see.
|
|
|
|
| |
He'll be working on the DOS emulator, among other things.
|
|
|
|
|
|
| |
primarily in the SCSI arena.
Welcome aboard, Matt!
|
|
|
|
|
|
| |
Would someone with root privileges please be so kind to create
him an account on freefall ? Thanks a lot !
ack'ed by: core
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
itojun!
Your first assignment (like everyone else) is to move yourself from
the "additional contributors" to "developers" section in the
handbook. :)
|
|
|
|
|
|
|
| |
of UUPC, and promised to do whatever maintenance will be required for
our UUCP.
Btw., he's got UID 700...
|
| |
|
|
|
|
| |
be doing a better job now. (fingers crossed)
|
| |
|
| |
|
|
|
|
| |
addresses
|
|
|
|
|
|
| |
from the verifymsg hook to clean the log message on all commits including
remote ones, cvs commit -m 'msg' and cvs commit -F msgfile, rather than
just local commits on freefall with the editor.
|
| |
|
| |
|
|
|
|
| |
(or somebody) deleted the real avail,v file from /home/ncvs/CVSROOT(!)
|
|
|
|
|
| |
it's version digits into double digits, eg: cvs-1.10.0. Bump minimum
number for the version installed on freefall.
|
| |
|
|
|
|
|
|
|
| |
being sent to cvs-*@freebsd.org. Also, some minor cosmetic tweaks.
Reviewed by:
Submitted by:
Obtained from:
|
|
|
|
|
|
| |
Reviewed by:
Submitted by:
Obtained from:
|
|
|
|
|
|
|
|
|
|
|
| |
- suppress duplicate copies of mail to mailing lists when directories
are crossed. I removed the use of dbm files for simplicity and used
flat text files, but I kinda forgot about the implicit unique keys, so
work around it now.
- Don't log the action header if it's unchanged from the last directory.
It could still possibly be duplicated, but I'm pretty sure the branch
tag hashing will stop that from happening. (I hope :-)
- add an extra 5 chars to the directory column
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
problem...
No seriously, this is a major revamp of the log scripts in preperation
for an update to a later version of cvs (ie: 1.9.8)
Among the changes:
- lots of dead code and useless stuff ripped out
- lots of things rewritten and/or redesigned
- support new message format that's passed from cvs to the log
script so that commits to individual files on branches works.
- perl5 now *required* due to above (hashes of arrays @{$var${tag}})
- commit message format slightly changed due to per-file branches
- new mailing lists (well, from last year) and commitlogs supported,
eg: cvs-contrib, cvs-tools, etc
- more space for filenames on each line before wrapping.
- more intelligent line wrapping, alignment should be better.
- no more insanely long Subject: lines.
There are more changes in the pipeline, including being able to do a
partial commit message when cvs is aborted in the middle of a commit,
but since the diff of the changes is now much larger than the file
itself, and we need the new cvs support, commit this now.
It's had a fair bit of testing in a private copy of the cvs tree, but
it's still not all that unlikely that there won't be things I've missed.
|
|
|
|
| |
PR:
|
| |
|
|
|
|
| |
an older version!
|
|
|
|
|
| |
much use anyway and just makes people reluctant to use 'cvs add' even
though it's more appropriate than 'cvs import' in several cases.
|
|
|
|
| |
for imports..
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
code, as well as simplifying some admin procedures.
The main change is to stop multi-directory commits only having the subject
info of the last directory, and not being sent to all the lists, and not
being logged to the appropriate commitlogs.
updateCVSROOT is gone (yay!), it's functionality is replaced by a cvs-1.6
feature - the 'checkoutlist' file, which is designed explicitly for this.
This will stop the easy-import users from getting told the mailing list
is out of date when a committer has been added but had missed out on being
put on the cvs-committers mailing list.
Update the comments and info in the *info files with the cvs-1.6 headers,
this fixes a few typos, clarifys some things, corrects some misleading
comments, etc.
Some stub files added to indicate how new cvs-1.6+ functionality is used,
but left commented out (taginfo, cvswrappers, etc)
All hard-coded references to /home/ncvs are changed back to $CVSROOT
(as suggested to me by bde) now that cvs-1.6+ makes a special effort
to ensure $CVSROOT is always set. This allows the $CVSROOT files to be
used elsewhere (eg: for testing) with much less pain.
mkavail is history as well, it was often being forgotten. cvs-committers
now takes the user list from /etc/group:ncvs via a trivial perl script.
This is so that we still have the ability to temporarily disable commit
access via 'avail' without cutting off the cvs-committers mailing list.
Since /etc/group editing is still required, this is not a new admin
overhead. If we ever change so that membership of "ncvs" is not required
(eg: /usr/bin/cvs becomes setgid and access control is via avail) then
we are going to have to do it some other way. (I have ideas)
I have tested this on my machines, but it is possible that I have missed
something. As usual, please yell if I've botched it.
|
|
|
|
|
| |
the perl construct "local($dir) = @_; " - perl warns about it, but
it doesn't seem to work if I directly assigned $dir....
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
I've been using this code in this approximate form for about 6 months now.
I'm keen to hear how useful this is/isn't for people.
It gives an unambiguous indication of how big the commit is, and the
revision numbers are collected into one place to make it easier to find and
follow all the parts of a commit over multiple files.
|
| |
|
|
|
|
| |
incremental steps.. Please forgive the number of commits....
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
in CVSROOT. The idea being that the modules file is changed to run
updateCVSROOT instead of mkmodules. This will eventually do the necessary
syncing that is currently done manually.
|
|
|
|
|
| |
Also, try a simple sanity check in "commitcheck" to try and head off
accidental commits on thud over NFS...
|
|
|
|
| |
off newlines. :-O
|
|
|
|
|
|
|
|
|
|
| |
set it. I'm still at a loss to explain why getlogin and `logname`
(which make a supposedly secure system call) are returning somebody else's
username when cvs (a non privileged process) is run on the end of a rsh.
If I do: rsh freefall 'print getlogin' it always seems to work...
(If this doesn't work after this commit, I might commandeer Jeffrey Hsu's
login.. :-) This commit may say 'hsu' though.)
|
|
|
|
|
| |
that the mail process always gets it right and that's a subshell of the perl
script log_accum.pl, so it's worth giving this a go.
|
|
|
|
|
| |
Remove debugging output again.. (which proved that getlogin returns the
wrong value sometimes..)
|
|
|
|
| |
I can see how 'hsu' is getting attributed with some of my commits.
|
|
|
|
|
|
|
|
|
|
| |
quits without saving.
Previously, it would cause cvs to abort the commit without giving
any warning.
Now, it does that cvs normally does when the user quits without saving,
ie: ask if you want to abort, or use the empty message, or re-edit.
|
|
|
|
|
|
|
|
| |
on empty log messages, far far better than allowing the commit.
I will have to wait to talk to Peter on a longer term fix.
Submitted by: David Greenman
|
|
|
|
| |
Reviewed by: rgrimes
|
|
|
|
| |
This got past both Rod and I.. :-(
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This hook is launched by cvs instead of your editor when commiting.
cvsedit runs the editor for you, and does some post-processing on the
file after you quit.. It does the following:
- Remove trailing whitespace
- Collapse multiple blank lines
- Removes empty "Reviewed-by" etc lines, stopping cvs from putting them
into the rcs log.
- Removes leading and trailing blank lines..
- maintains the file timestamps if no changes are made, allowing you to
abort a commit properly.
(Sadly, I didn't have time to get the AI code running that was meant to
check your code for you and find any bugs in your committed code.. :-)
Reviewed by: Rod Grimes
|
| |
|
| |
|
|
|
|
|
| |
CVS:
CVS:
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Reviewed by:
Submitted by:
Obtained from:
Are blank, after this commit, cvs will remove them from the Log:
section.
|
|
|
|
|
|
|
|
|
|
| |
Branch: detection logic into this. It's only 8 new lines, but due
to the learning curve it took me 3 hours to write them :-(.
Also fixed the $FreeBSD$ keyword to be $Id$ since it is turned off.
Next.. auto deletion of blank ``Reviewed, Submitted and Obtained" lines.
That should only take an hour more :-)
|
|
|
|
|
|
| |
/usr/local.
Submitted by: asami
|
|
|
|
| |
Currently it contains '*.info' and '*.db' entries.
|
|
|
|
| |
WTF I'm committing again.
|
|
|
|
|
|
|
|
|
| |
to get the commit timestamp. This makes the time stamps comparable.
I'm rather in favour for using gmtime() instead of localtime(), but i
guess i cannot convince all you american guys. :)
I'll let up the RCS checkout to our CVS master...
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
automagically each and any time it's changed. Change log_accum.pl
to send to the new cvs-committers mailing list that uses this
file. This should cut down on the size of our monster cvs mail
headers considerably! :-)
Many thanks to Gary Clark II for these changes.
Submitted by: gclarkii
|
|
|
|
|
| |
compact so you have a chance to see the file list when composing your message.
CVS:
|
|
|
|
| |
CVS:
|
|
|
|
|
| |
an Obtained from: line. This was my suggestion so I added since I was
in the file anyway. If people disagree they can easily change it.
|
| |
|
|
|
|
| |
Submitted by:
|
|
|