-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gitk: Add a basic support of SHA256 repositories into Gitk #979
base: master
Are you sure you want to change the base?
Conversation
Welcome to GitGitGadgetHi @rosti-il, and welcome to GitGitGadget, the GitHub App to send patch series to the Git mailing list from GitHub Pull Requests. Please make sure that your Pull Request has a good description, as it will be used as cover letter. Also, it is a good idea to review the commit messages one last time, as the Git project expects them in a quite specific form:
It is in general a good idea to await the automated test ("Checks") in this Pull Request before contributing the patches, e.g. to avoid trivial issues such as unportable code. Contributing the patchesBefore you can contribute the patches, your GitHub username needs to be added to the list of permitted users. Any already-permitted user can do that, by adding a comment to your PR of the form Both the person who commented An alternative is the channel
Once on the list of permitted usernames, you can contribute the patches to the Git mailing list by adding a PR comment If you want to see what email(s) would be sent for a After you submit, GitGitGadget will respond with another comment that contains the link to the cover letter mail in the Git mailing list archive. Please make sure to monitor the discussion in that thread and to address comments and suggestions (while the comments and suggestions will be mirrored into the PR by GitGitGadget, you will still want to reply via mail). If you do not want to subscribe to the Git mailing list just to be able to respond to a mail, you can download the mbox from the Git mailing list archive (click the curl -g --user "<EMailAddress>:<Password>" \
--url "imaps://imap.gmail.com/INBOX" -T /path/to/raw.txt To iterate on your change, i.e. send a revised patch or patch series, you will first want to (force-)push to the same branch. You probably also want to modify your Pull Request description (or title). It is a good idea to summarize the revision by adding something like this to the cover letter (read: by editing the first comment on the PR, i.e. the PR description):
To send a new iteration, just add another PR comment with the contents: Need help?New contributors who want advice are encouraged to join [email protected], where volunteers who regularly contribute to Git are willing to answer newbie questions, give advice, or otherwise provide mentoring to interested contributors. You must join in order to post or view messages, but anyone can join. You may also be able to find help in real time in the developer IRC channel, |
Invalid author email in 4cc3f1f: "[email protected]" |
Invalid author email in 96f17f5: "[email protected]" |
/preview |
Error: User rosti-il is not permitted to use GitGitGadget |
/submit |
Error: User rosti-il is not permitted to use GitGitGadget |
Invalid author email in 570cd9c: "[email protected]" |
/preview |
Error: User rosti-il is not permitted to use GitGitGadget |
I know I don't have permission to use /preview of GitGitGadget yet, but as a side effect it fixes following GutHub issue:
|
@dscho please /allow me. |
I am on vacation, but okay. |
/allow |
User rosti-il is now allowed to use GitGitGadget. WARNING: rosti-il has no public email address set on GitHub |
/submit |
Invalid author email in 570cd9c: "[email protected]" |
@bk2204 since you are driving a lot of the SHA-256 effort forward, would you maybe interested in taking this patch under your custody? It would appear that @rosti-il is unwilling to disclose their email address (which would be required by the Git project to accept the patch). |
Signed-off-by: Rostislav Krasny <[email protected]>
/submit |
Submitted as [email protected] To fetch this version into
To fetch this version to local tag
WARNING: rosti-il has no public email address set on GitHub |
I unfortunately can't do that because while I'm familiar with many languages and can bumble my way through many others, I've never worked with Tcl and can't respond to any feedback on the patch since I don't know anything about the language. Sorry. |
On the Git mailing list, Junio C Hamano wrote (reply to this):
|
On the Git mailing list, Ævar Arnfjörð Bjarmason wrote (reply to this):
|
User |
On the Git mailing list, Felipe Contreras wrote (reply to this):
|
User |
Hello everybody. I created this PR almost a year ago, is there any general progress with supporting SHA256 in gitk? Even some other's patch/PR? |
@rosti-il if I were you, I'd just reply on-list with a gentle ping. |
On the Git mailing list, Rostislav Krasny wrote (reply to this):
|
User |
This PR makes Gitk working on both SHA256 and SHA1 repositories without errors/crashes.
I made it by changing and testing the
gitk
script of Git for Windows version 2.32.0.windows.1 that is a little bit different than the mainstream 2.32.0 version.Still not fixed functionality:
[1] There is the "Auto-select SHA1 (length)" configuration preference that affects "Copy commit reference" on both SHA1 and SHA256 repositories.
A new "Auto-select SHA256 (length)" configuration preference should be added and used on SHA256 repositories instead of the old one. Since I'm not familiar with Tcl/Tk and this issue isn't critical I didn't implement it.
cc: Ævar Arnfjörð Bjarmason [email protected]
cc: Felipe Contreras [email protected]
cc: Rostislav Krasny [email protected]