| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
| |
This updates the mode-line for most of our generated files so that
they include file type information so they will be properly syntax
highlighted on github.
This does not make any other functional changes to the files.
[Note: Commit message rewritten by Yves]
|
|
|
|
|
|
|
|
|
| |
Previously you could use seekdir/readdir on Windows to examine
the memory space of the process until this triggered SIGSEGV.
Adds a new test file t/win32/seekdir.t
[Note: patch fixup and squash by Yves]
|
| |
|
|
|
|
|
|
|
| |
- Specifically calls out the possible invocations
- Breaks out the specific use cases and why to use them
- Notes the things to avoid and why in clearer language
- Update .mailmap so that tests all pass
|
|
|
|
|
|
|
|
| |
Signed-off-by: lilinjie <lilinjie@uniontech.com>
Committer: Li Linjie is now a Perl author.
Run Porting/updateAUTHORS.pl to update .mailmap
|
| |
|
|
|
|
|
|
|
| |
Moved declaration of object p.
For: Issue: https://github.com/Perl/perl5/issues/20485
p.r.: https://github.com/Perl/perl5/pull/20486
|
|
|
|
|
| |
Adds a section to `perldiag` that details what the `Unimplemented` error
is, caused by executing an ellipsis ("...;") statement.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes #20033.
When building on Windows with Strawberry 5.32.1 (gcc 8.3.0) as the toolchain,
the Errno.pm is created by a script Errno_pm.pl, which takes output from the
compiler to find headers.
A subset of these headers requires them to only be included by some specific
headers. Previously the header order was effectively random and this
occasionally caused build errors (that further were never detected).
The get_files() is now returning the header names in the order the compiler
saw them which insures they are in the right order.
|
| |
|
|
|
|
| |
And remove the duplicate for "vividsnow" that this found.
|
|
|
|
|
| |
Contributor has requested they be excluded from our contributor
databases.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A number of devs have noted and raised concerns that having .mailmap
entries where the LHS and RHS of the entry is redundant. A few have also
expressed the view that this exposes unnecessarily exposes their email
address in an easily harvestible form.
On the technical level as far as git specifically is concerned it is
true this data is redundant, as git uses .mailmap to transform user data
that match the RHS of an entry into the value on LHS, and when they are
the same obviously it is a no-op. However on the technical level for our
infra these entries are not redundant. We can use them to identify and
correctly respond to many cases of manual update of the AUTHORS file,
for instance changing ones preferred name. With the .mailmap entries we
have the data to identify the old preferred name, and join it together
with the unchanged email for the user and then automatically update
their .mailmap entries. This is why these entries were created
originally.
However, I believe that this functionality is not useful enough to
require us to have discussions with contributors on this subject on a
regular basis. We can add command line options that allow people to
change the AUTHORS file and the .mailmap file properly, so we can drop
the "redundant" data and avoid the need to talk about why it is there.
The required functionality for changing names will come in a follow up
patch in this PR.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This add a new file Porting/exclude_contrib.txt to hold a list
of base64 SHA-256 digests of the user name and email who should be
excluded.
This adds the options
--exclude-me
--exclude-contrib=NAME_AND_EMAIL
--exclude-missing
to add exclusions in different ways. --exclude-me uses the git
credentials for the current user, --exclude-contrib expects a name
and email, and --exclude-missing excludes someone who is missing from
the change log.
When excluding someone their name will be removed from AUTHORS if it is
already listed, and the relevant entries to .mailmap will be removed,
and if necessary additional exclusion entries will be added for any of
their old identities which were mentioned in .mailmap.
This feature will be used in a later patch to resolve GH issue #20010.
|
|
|
|
|
|
|
| |
A. Sinan Unur was listed twice in AUTHORS, under Sinan Unur
as well. This removes the dupe.
This is in prep for various changes to the updateAUTHORS.pl process.
|
| |
|
|
|
|
| |
real module version
|
|
|
|
| |
Length just isn't needed, and often took more cpu-time than the actual regex.
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes the following warning on illumos based platforms:
Cwd.xs:27:0: warning: "SYSNAME" redefined
#define SYSNAME "$SYSNAME"
In file included from ../../perl.h:1111:0,
from Cwd.xs:8:
/usr/include/sys/param.h:184:0: note: this is the location of the previous definition
#define SYSNAME 9 /* # chars in system name */
|
| |
|
|
|
|
|
| |
As mentioned in https://lists.llvm.org/pipermail/llvm-dev/2015-July/088122.html
and https://github.com/llvm/llvm-project/issues/24625 building with clang-cl currently fails due to the declaration of __PL_nan_u.
By declaring it like this, cl and clang-cl are happy to parse it.
|
|
|
|
|
|
|
|
| |
This commit is actually by the committer, and is intended to ensure that
someone looking for what the author wrote can find it. It took me a while
to get a email address for him or I would have done this in eda35008b17e739922
which is where his work on the _squeeze() split key algorithm was added.
Credit where credit is due and all of that. Thanks Ilya.
|
|
|
|
| |
Probably we should have a test so people remember to do this.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change updates AUTHORS with multiple missing contributors to the
project. It updates .mailmap so that the preferred email for each
developer matches what is in AUTHORS (sometimes changing the AUTHORS
entry, sometimes changes the .mailmap entry or entries to achieve this
goal. It also adds a new tool, Porting/UpdateAuthors.pl which can be
used to automatically update the relevant data.
The general idea is that if you run Porting/UpdateAuthors.pl any never
developers will be added to AUTHORS, and new entries will be added to
the .mailmap file. The aim is that the only data we need to have to
manage both files is the data in both files and the commit history
itself. There is NOT embedded special datasets in the tool.
The idea is that *every* developer, be it author or committer has at
least one entry in .mailmap, and that the vast majority of the email
data we have for commits is mapped to corresponding entry in the AUTHORS
file. Furthermore the .mailmap file is expected to have an entry for
every distinct email ever used by a developer on the project.
If you run Porting/UpdateAuthors.pl the tool will analyze all the
commits in the projects history, and update either or both the .mailmap
and AUTHORS file appropriately. If an existing developer adds a commit
which either has the same name or email as is listed already then it
will DTRT and update the .mailmap with the appropriate mappings. If a
new developer adds a commit then it will DTRT and update both the
.mailmap and the AUTHORS file with that developers details.
Every single existing distinct name/email combination has been added to
the mailmap, and matched to AUTHORS data. In some case where there was
conflicting or missing data I used an educated guess, contacted the
developer myself, or verified the email with the email provider. Eg.
gmail.com will helpfully resolve gmail email addresses to their name if
you simply type the email address into a new mail.
testing
testing
fixup
fixup
fixup
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This provides a single-point-of-update for perlgov automation. We can
use email address as a key and pull out the human name. I could have
used AUTHORS for this, but I think it would have required a little more
code.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
the .mailmap file allows git to correct committer details in things like
git log. Compare `git log --author=yves` with `git log --use-mailmap --author=yves`
the former finds commits I have made using old email addresses, the latter
finds nothing as the corrected version of my name is "Yves Orton". Conversly
`git log --use-mailmap --author=Yves` will find pretty much *all* of my commits.
|