Closed zvezdochiot closed 3 years ago
I like the idea, because the thing "50 commits ahead, 26 commits behind" is irritating me also. But I am thinking if the same thing may happen again ?
OK. Let it repeat itself. Nothing prevents me from repeating.
Don't change anything for 1 hour. I am doing a shenanigans.
Dont do this today. I have not commited the last change (move icons to data/) in my repo
I am working on creating AppImage. It may take one or two days to commit the last change.
Ok. I noticed. I'll wait.
PS: Add a message when ready.
Ok. One more thing, I want to use that 96px photoquick icon for desktop icon (instead of 32px). Because in desktop (both windows and linux) the 32px is scaled and becomes little hazy.
Although what to pull. I'll do a trial sync now, no tags sync. And after a couple of days, full.
✔️
Now you can compare.
@ksharindam .
⚠️ If you are working on the code of the current repo, rename it, clone it anew and replace the code with the one you are working with. (git history changed: .git
directory)
PS: ℹ️ On your repo, apply:
sed -i -e 's/\t/ /g' *.cpp *.h
@ksharindam .
Is GPL-3.0 really important to you? Or is the question of changing to PDM-1.0 (https://github.com/ImageProcessing-ElectronicPublications/python-pdf-jpeg-extract/blob/master/LICENSE) appropriate?
Yes, i like to keep it GPL licenced.
On Sat, 5 Jun, 2021, 2:18 PM звездочёт, @.***> wrote:
@ksharindam https://github.com/ksharindam .
Is GPL-3.0 really important to you? Or is the question of changing to PDM-1.0 ( https://github.com/ImageProcessing-ElectronicPublications/python-pdf-jpeg-extract/blob/master/LICENSE) appropriate?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ImageProcessing-ElectronicPublications/photoquick/issues/34#issuecomment-855207621, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEKWXPTHTPEGJNX4JTB7B6TTRHQFVANCNFSM46EGAIRA .
👍 Ok. No comment.
@ksharindam .
It is necessary to bring the documentation to the original. Don't spare commits. I will still do sync after fine-tuning.
And PS: ℹ️ On your repo, apply:
sed -i -e 's/\t/ /g' *.cpp *.h
You have done sync, now what to do ?
Hi @ksharindam .
Synchronization is rather poor, most of the differences are related to tabs. You not did:
sed -i -e 's/\t/ /g' *.cpp *.h
Because of this, significant differences are difficult to see.
@ksharindam .
Now all the differences are visible. At this stage, that's enough. Then you can repeat.
I can clone your repo by making all the differences in the code with the last summary commit. This will result in the loss of own story and comments, but will return the ability to compare differences normally.
How do you like this proposal?