rom1v

They have to use one key per app, otherwise independent app could end up sharing some permissions (IIRC).

In addition to F-Droid on the device, I'd love an F-Droid "package manager client" on a computer, that allows installing apps on an Android device via adb:

    # update repo lists
    fdr update
    
    # upgrade all apps on the connected device
    fdr upgrade
    
    # search packages
    fdr search vlc  # lists org.videolan.vlc
    
    # install on the device
    fdr install org.mozilla.firefox
    
    # download the apk
    fdr download org.mozilla.firefox
    
    # uninstall
    fdr uninstall org.mozilla.firefox 

Of course, all operations would verify the signatures first.

"I play the piano" or "I play piano"?

> `git history fixup` fixes an old commit that has something wrong in it, then autorebases all your branches to match.

Simplifying `git rebase -i` is a great idea, but unfortunately, that does not match my workflow.

I always keep an history of my branches. For example, when I develop a feature, the first version of the branch is `myfeature.1`, then `myfeature.2`, and so on. This is useful because I can retrieve an old version when something behaves differently in a newer one. (And no, `git reflog` will not help)

This has saved me multiple times. For example, I can determine that a problem was introduced between `myfeature.58` and `myfeature.59`. If the "feature" contains 15 commits, I do:

    git range-diff myfeature.58~15..myfeature.58 myfeature.59~15..myfeature.59

This lets me see the changes between the 2 versions, commit by commit (even if they don't have the same base).

I don't want all the branches containing a commit to be rebased automatically (I already try using tags for old versions instead, but this does not quite fit).

> The difference in the code is exactly one word: value.

What is unclear to me is why the decision to use a Point instance as a value or as a reference is made in the class definition rather than by the caller.

> Point[] point = new Point[10];

For the same class, I might need an array of values in one place and an array of references elsewhere within the same codebase.

--keep-active ;)

Please post a link to the issue.

Are the years intended to be read in octal?

> One of the most important themes we hear from the developer community is the need for more lead time to adapt to changes

No, it's not.