Sorry for the "chain mail"
That should have been the "-C" and "-v" flags.
hg log -vfC [FILE]
On 04/23/10 10:57 AM, Keith Mitchell wrote:
Quick follow-up:
Add a "-p" flag ("hg log -fp [FILE]") to track non-obvious files that
changed names.
- Keith
On 04/23/10 09:52 AM, Keith Mitchell wrote:
Hi all,
I just want to remind everyone about the specifics of the copyright
change. The portion I'm seeing missed most is that the changed
copyrights are following option "c" from section 2 below (with first
date being the current date in the file). As all our source code is
versioned in mercurial, all changes in our gate should be able to
follow the format from section "a" (initial date), or section "b"
(date of addition to source control).
You can use the command "hg log -f [FILE]" to determine the first
revision that a file was in slim_source. Follow that with an "hg up
-r [revision]" and check the copyright date on the file as originally
entered in slim_source, and use that date. You can also search/browse
the repository history by running "hg serve" against a local repo, or
by navigating to "http://indiana-build.central:8080"; internally.
Please let me know if you have any questions.
Thanks,
Keith
On 04/ 1/10 10:18 AM, Keith Mitchell wrote:
Hello all,
The slim_source gate will follow in O/N's footsteps, and adopt the
new copyright format starting with build 138. Please maintain the
existing format through build 137, and begin using the new format
after that. Details from the ON heads-up are below.
The developer/build/onbld tools will be updated to reflect those
changes with 138 - if you're using tools prior to that you'll need
to take extra care to ensure that copyright's meet the required format.
Thanks,
Keith
http://static.opensolaris.org/on/flagdays/pages/20100324114440.html
Greetings gatelings,
The change of copyrights in source code from Sun to Oracle that
everyone
knew has been coming is finally almost here. For anyone pushing code
changes to the remainder of build 137: stay the course. But the first
push of build 138 next Tuesday will update the prototypes, the boot
banners,
/etc/motd and the tools to check for the new format, so anyone
planning
changes for build 138 or later, below are the details on the new
format.
The paradigm is that new files will be created with new copyrights,
and
old files will be updated per the rules below when modified. But
there
is no need to do pro-active updates; only update a file's copyright
when
you are already modifying that file.
Please send any questions to .
1. When a new source file is created, it must contain the following
Oracle
copyright statement.
Copyright (c) YEAR, Oracle and/or its affiliates. All rights
reserved.
Where YEAR = the year in which the file is created.
Example:
Copyright (c) 2010, Oracle and/or its affiliates. All rights
reserved.
NOTE: Always use the "(c)" notation, even if the copyright
character is
available on your system, to avoid conflicts and confusion.
2. When an existing Sun source file is modified, the Sun copyright is
removed and replaced by an Oracle copyright:
Copyright (c) YEAR1, YEAR2, Oracle and/or its affiliates. All
rights reserved.
Where YEAR1 = one of the following options, in priority order:
a. The year in which the Sun file was created, if easily
determined.
Note: for ON, this is generally not easily determined;
see rule b.
b. The year in which the Sun file was introduced into the
source
hierarchy, if easily determined. Note: for ON, this is
easily
determined: run:
% /ws/onnv-gate/public/bin/start-date usr/src/foo usr/src/bar ...
c. The year listed in the Sun copyright currently in the file.
NOTE: For third-party code that was later modified by Sun and
marked
with a Sun copyright, YEAR1 = the year in which the Sun
copyright was
introduced into the file, if easily determined. If not, use
the year
listed in the Sun copyright currently in the file.
Where YEAR2 = the latest year in which the file is modified.
Example:
Copyright (c) 1997, 2010, Oracle and/or its affiliates. All
rights reserved.
NOTE: If the year of creation and the year of modification are
the same,
use the notation outlined in #1 above. If EngineerA modifies a
Sun file
in 2010 that was created in 2010, EngineerA removes the Sun
copyright
and inserts an Oracle copyright that only contains a 2010
copyright:
Copyright (c) 2010, Oracle and/or its affiliates. All rights
reserved.
3. The instructions noted above also apply to "Portions Copyright
YEAR,
Sun..." statements that are mostly used in manual pages.
Example:
Portions Copyright (c) YEAR, Sun Microsystems, Inc. All Rights
Reserved.
is replaced with:
Portions Copyright (c) YEAR1, YEAR2, Oracle and/or its
affiliates. All
rights reserved.
Where YEAR1 and YEAR2 are determined per the instructions in #2
above.
-- John
http://blogs.sun.com/jbeck
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
