Skip to content
This repository was archived by the owner on Apr 12, 2021. It is now read-only.
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: NixOS/nixpkgs-channels
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 6148f6360310
Choose a base ref
...
head repository: NixOS/nixpkgs-channels
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 3829979d8d29
Choose a head ref
  • 5 commits
  • 5 files changed
  • 5 contributors

Commits on Jul 16, 2020

  1. audacious: 3.9 -> 4.0.5

    @gebner
    gebner committed Jul 16, 2020

    Verified

    This commit was signed with the committer’s verified signature. The key has expired.
    servalcatty
    GPG key ID: 4A2AAAA382F8294C
    Expired
    Verified
    Learn about vigilant mode
    Copy the full SHA
    7f64f21 View commit details

Commits on Jul 17, 2020

  1. stale bot: spelling nit

    @lheckemann
    lheckemann committed Jul 17, 2020

    Verified

    This commit was signed with the committer’s verified signature. The key has expired.
    servalcatty
    GPG key ID: 4A2AAAA382F8294C
    Expired
    Verified
    Learn about vigilant mode
    Copy the full SHA
    3ecbb6a View commit details

  2. Add section on running ad-hoc Perl programs to the nixpkgs manual 

    Co-authored-by: Timo Kaufmann <timokau@zoho.com>
    @raboof @timokau
    raboof and timokau committed Jul 17, 2020

    Unverified

    This user has not yet uploaded their public signing key.
    GPG key ID: CED392DE0C483D00
    Learn about vigilant mode
    Copy the full SHA
    6093372 View commit details

  3. Merge pull request #93240 from gebner/audacious405 

    audacious: 3.9 -> 4.0.5
    @gebner
    gebner authored Jul 17, 2020

    Unverified

    This user has not yet uploaded their public signing key.
    GPG key ID: CED392DE0C483D00
    Learn about vigilant mode
    Copy the full SHA
    fd726a9 View commit details

  4. Merge pull request #86589 from raboof/document-running-perl-scripts-f… 

    …rom-the-shell

doc: add section on running ad-hoc Perl programs to the nixpkgs manual
    @Mic92
    Mic92 authored Jul 17, 2020

    Verified

    This commit was signed with the committer’s verified signature. The key has expired.
    stigtsp Stig
    GPG key ID: 10C838A306094775
    Expired
    Verified
    Learn about vigilant mode
    Copy the full SHA
    3829979 View commit details
Showing with 206 additions and 267 deletions.
  1. +1 −1 .github/stale.yml
  2. +176 −142 doc/languages-frameworks/perl.xml
  3. +27 −30 pkgs/applications/audio/audacious/default.nix
  4. +0 −92 pkgs/applications/audio/audacious/qt-5.nix
  5. +2 −2 pkgs/top-level/all-packages.nix
2 changes: 1 addition & 1 deletion .github/stale.yml
View file
Original file line number Diff line number Diff line change
@@ -17,7 +17,7 @@ pulls:
If this is still important to you and you'd like to remove the stale label, we ask that you leave a comment. Your comment can be as simple as "still important to me". But there's a bit more you can do:
If you received an approval by an unpriviledged maintainer and you are just waiting for a merge, you can @ mention someone with merge permissions and ask them to help. You might be able to find someone relevant by using [Git blame](https://git-scm.com/docs/git-blame) on the relevant files, or via [GitHub's web interface](https://docs.github.com/en/github/managing-files-in-a-repository/tracking-changes-in-a-file). You can see if someone's a member of the [nixpkgs-committers](https://github.com/orgs/NixOS/teams/nixpkgs-committers) team, by hovering with the mouse over their username on the web interface, or by searching them directly on [the list](https://github.com/orgs/NixOS/teams/nixpkgs-committers).
If you received an approval by an unprivileged maintainer and you are just waiting for a merge, you can @ mention someone with merge permissions and ask them to help. You might be able to find someone relevant by using [Git blame](https://git-scm.com/docs/git-blame) on the relevant files, or via [GitHub's web interface](https://docs.github.com/en/github/managing-files-in-a-repository/tracking-changes-in-a-file). You can see if someone's a member of the [nixpkgs-committers](https://github.com/orgs/NixOS/teams/nixpkgs-committers) team, by hovering with the mouse over their username on the web interface, or by searching them directly on [the list](https://github.com/orgs/NixOS/teams/nixpkgs-committers).
If your PR wasn't reviewed at all, it might help to find someone who's perhaps a user of the package or module you are changing, or alternatively, ask once more for a review by the maintainer of the package/module this is about. If you don't know any, you can use [Git blame](https://git-scm.com/docs/git-blame) on the relevant files, or [GitHub's web interface](https://docs.github.com/en/github/managing-files-in-a-repository/tracking-changes-in-a-file) to find someone who touched the relevant files in the past.
Loading