
* Fix minor FD leak in journal code. Closes: #754608 * direct: Fix handling of case where a work tree subdirectory cannot be written to due to permissions. * migrate: Avoid re-checksumming when migrating from hashE to hash backend. * uninit: Avoid failing final removal in some direct mode repositories due to file modes. * S3: Deal with AWS ACL configurations that do not allow creating or checking the location of a bucket, but only reading and writing content to it. * resolvemerge: New plumbing command that runs the automatic merge conflict resolver. * Deal with change in git 2.0 that made indirect mode merge conflict resolution leave behind old files. * sync: Fix git sync with local git remotes even when they don't have an annex.uuid set. (The assistant already did so.) * Set gcrypt-publish-participants when setting up a gcrypt repository, to avoid unncessary passphrase prompts. This is a security/usability tradeoff. To avoid exposing the gpg key ids who can decrypt the repository, users can unset gcrypt-publish-participants. * Install nautilus hooks even when ~/.local/share/nautilus/ does not yet exist, since it is not automatically created for Gnome 3 users. * Windows: Move .vbs files out of git\bin, to avoid that being in the PATH, which caused some weird breakage. (Thanks, divB) * Windows: Fix locking issue that prevented the webapp starting (since 5.20140707). # imported from the archive
38 lines
1.4 KiB
Markdown
38 lines
1.4 KiB
Markdown
Help make git-annex better!
|
|
|
|
## wiki gardening
|
|
|
|
This website is a wiki, so you can edit and improve any page.
|
|
|
|
Or, write a [[new_tip|tips]] explaining how to accomplish something with
|
|
git-annex.
|
|
|
|
## bug triage
|
|
|
|
People often file [[bugs]] on git-annex that are easily resolved by helping
|
|
them with a problem, and perhaps writing some documentation.
|
|
|
|
Many bugs are also filed without enough information
|
|
to reproduce the problem, and need to be tagged moreinfo and a comment
|
|
posted asking the submitter for details.
|
|
|
|
Joey spends a lot of time dealing with this kind of bug triage. If you can
|
|
take the time to pick a bug that is not marked as "confirmed" or "moreinfo"
|
|
from the list of [[bugs]], try to reproduce it and follow up either
|
|
confirming that the problem exists, or asking the submitter for more info,
|
|
you'll make Joey more productive!
|
|
|
|
## code contributions
|
|
|
|
[[download]] the source code and send patches!
|
|
|
|
If you know Haskell, git-annex has lots of Haskell code that
|
|
could be improved. See the [[coding_style]] and have at it.
|
|
|
|
If you don't know Haskell, git-annex has many other coding opportunities.
|
|
You could work to improve the Android port (Java etc) or improve the
|
|
Javascript and CSS of the git-annex webapp, or work on porting libraries
|
|
needed by the Windows port.
|
|
|
|
To send patches, either include the patch in a bug report (small patch)
|
|
or put up a branch in a git repository containing your changes.
|