Comments (18)
jonassmedegaard
commented on August 17, 2024
NB! Above changeset also includes my fix for issue #158 - in case for some reason you don't want to adopt that.
from po4a.
mquinson
commented on August 17, 2024
What about proposing a MR on salsa, then? https://salsa.debian.org/mquinson/po4a
from po4a.
mquinson
commented on August 17, 2024
Can it be that your project on salsa is closed and not public? It's not to be found on salsa: https://salsa.debian.org/search?utf8=%E2%9C%93&search=po4a
from po4a.
jonassmedegaard
commented on August 17, 2024
Quoting Martin Quinson (2018-11-01 18:15:33)
Can it be that your project on salsa is closed and not public? It's
not to be found on salsa:
https://salsa.debian.org/search?utf8=%E2%9C%93&search=po4a
Sorry - should be accessible now!
…--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
from po4a.
toddy15
commented on August 17, 2024
Hi Jonas,
I've just looked at your fork on salsa -- it seems that there's only the copyright line included, I cannot see anything for the markdown parser. Is that change still included?
Regards,
Tobias
from po4a.
jonassmedegaard
commented on August 17, 2024
Quoting Dr. Tobias Quathamer (2018-11-03 13:50:24)
I've just looked at your fork on salsa -- it seems that there's only
the copyright line included, I cannot see anything for the markdown
parser. Is that change still included?
Sorry for not mentioning here. You guessed correctly that it is not
included: You requested a PR for the copyright line alone, and
apparently Gitlab can only fork to a git by same name so I replaced this
changeset by the minimal licensing fix, and when that is solved we can
move on to this larger one.
If you know of a better approach (except using Github) then I am open to
suggestions - I am not fluent in doing PRs.
- Jonas
…--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
from po4a.
toddy15
commented on August 17, 2024
Ah, OK. Well, the copyright line is now included in git, so you may switch your fork back to the larger markdown patch.
from po4a.
jonassmedegaard
commented on August 17, 2024
Quoting Dr. Tobias Quathamer (2018-11-03 13:50:24)
I've just looked at your fork on salsa -- it seems that there's only
the copyright line included, I cannot see anything for the markdown
parser. Is that change still included?
Please look again now: Git with only copyright changeset has been
replaced with git containing markdown changeset - based on upstream code
as of today.
- Jonas
…--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
from po4a.
mquinson
commented on August 17, 2024
Hello,
On Sat, Nov 03, 2018 at 06:47:47AM -0700, Jonas Smedegaard wrote:
If you know of a better approach (except using Github) then I am open to
suggestions - I am not fluent in doing PRs.
I'm very aware of the issues with github, and I moved most of my
projects out of there, but we just moved po4a from alioth to github,
and I fear that we could break the momentum by moving again so soon.
This is the only reason why we're still on github, I think. For the
time being, we maintain a fork synchronized on salsa.d.o specifically
for the ones who don't want to use github.
So, the best move for you is to fork the project on salsa and forget
about github. Then, it would be wonderful if you could learn about MR
(Merge Requests -- that's how gitlab calls PR Pull Request). Github
new TOS are concerning, but the workflow they invented is really
great. We are really lucky that gitlab pushed this further.
Cheers,
Mt.
from po4a.
jonassmedegaard
commented on August 17, 2024
Quoting Martin Quinson (2018-11-03 15:44:04)
On Sat, Nov 03, 2018 at 06:47:47AM -0700, Jonas Smedegaard wrote:
>
> If you know of a better approach (except using Github) then I am
> open to suggestions - I am not fluent in doing PRs.
I'm very aware of the issues with github, and I moved most of my
projects out of there, but we just moved po4a from alioth to github,
and I fear that we could break the momentum by moving again so soon.
This is the only reason why we're still on github, I think. For the
time being, we maintain a fork synchronized on salsa.d.o specifically
for the ones who don't want to use github.
So, the best move for you is to fork the project on salsa and forget
about github. Then, it would be wonderful if you could learn about MR
(Merge Requests -- that's how gitlab calls PR Pull Request). Github
new TOS are concerning, but the workflow they invented is really
great. We are really lucky that gitlab pushed this further.
Where on Salsa?
I see only https://salsa.debian.org/debian/po4a which seems to not
contain upstream git commits - only upstream release tarball imports.
- Jonas
…--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
from po4a.
jonassmedegaard
commented on August 17, 2024
Quoting Jonas Smedegaard (2018-11-03 16:26:49)
Quoting Martin Quinson (2018-11-03 15:44:04)
> On Sat, Nov 03, 2018 at 06:47:47AM -0700, Jonas Smedegaard wrote:
> >
> > If you know of a better approach (except using Github) then I am
> > open to suggestions - I am not fluent in doing PRs.
>
> I'm very aware of the issues with github, and I moved most of my
> projects out of there, but we just moved po4a from alioth to github,
> and I fear that we could break the momentum by moving again so soon.
> This is the only reason why we're still on github, I think. For the
> time being, we maintain a fork synchronized on salsa.d.o specifically
> for the ones who don't want to use github.
>
> So, the best move for you is to fork the project on salsa and forget
> about github. Then, it would be wonderful if you could learn about MR
> (Merge Requests -- that's how gitlab calls PR Pull Request). Github
> new TOS are concerning, but the workflow they invented is really
> great. We are really lucky that gitlab pushed this further.
Where on Salsa?
I see only https://salsa.debian.org/debian/po4a which seems to not
contain upstream git commits - only upstream release tarball imports.
Ah, if you mean that there are no fork at Salsa maintained by you, but
you encourage me to create one from scratch, syncronized with upstream
git at Github, then I believe that is _exactly_ what I have done now.
- Jonas
…--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
from po4a.
mquinson
commented on August 17, 2024
----- Le 3 Nov 18, à 16:26, Jonas Smedegaard <[email protected]> a écrit :
Quoting Martin Quinson (2018-11-03 15:44:04)
> For the
> time being, we maintain a fork synchronized on salsa.d.o specifically
> for the ones who don't want to use github.
> So, the best move for you is to fork the project on salsa and forget
> about github. Then, it would be wonderful if you could learn about MR
> (Merge Requests -- that's how gitlab calls PR Pull Request). Github
> new TOS are concerning, but the workflow they invented is really
> great. We are really lucky that gitlab pushed this further.
Where on Salsa?
I see only https://salsa.debian.org/debian/po4a which seems to not
contain upstream git commits - only upstream release tarball imports.
https://salsa.debian.org/search?utf8=%E2%9C%93&search=po4a
The third one, not the fourth one. More specifically:
https://salsa.debian.org/mquinson/po4a
Mt
from po4a.
jonassmedegaard
commented on August 17, 2024
Quoting Martin Quinson (2018-11-03 18:19:20)
----- Le 3 Nov 18, à 16:26, Jonas Smedegaard ***@***.***> a écrit :
> Quoting Martin Quinson (2018-11-03 15:44:04)
> > For the
> > time being, we maintain a fork synchronized on salsa.d.o specifically
> > for the ones who don't want to use github.
> > So, the best move for you is to fork the project on salsa and forget
> > about github. Then, it would be wonderful if you could learn about MR
> > (Merge Requests -- that's how gitlab calls PR Pull Request). Github
> > new TOS are concerning, but the workflow they invented is really
> > great. We are really lucky that gitlab pushed this further.
> Where on Salsa?
> I see only https://salsa.debian.org/debian/po4a which seems to not
> contain upstream git commits - only upstream release tarball imports.
https://salsa.debian.org/search?utf8=%E2%9C%93&search=po4a
The third one, not the fourth one. More specifically:
https://salsa.debian.org/mquinson/po4a
Thanks.
Perhaps I was not at the front page when I searched, and that is
required to locate personal git repos.
Re-pushed my changeset, now linked to yours, and did an MR:
https://salsa.debian.org/mquinson/po4a/merge_requests/72
- Jonas
…--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
from po4a.
toddy15
commented on August 17, 2024
Am 03.11.2018 um 18:50 schrieb Jonas Smedegaard:
Thanks.
Perhaps I was not at the front page when I searched, and that is
required to locate personal git repos.
Re-pushed my changeset, now linked to yours, and did an MR:
https://salsa.debian.org/mquinson/po4a/merge_requests/72
Hi,
thanks a lot for this, I've merged it on github. The MR on salsa could
now be closed. Sorry for the inconvenience of not doing this automatically.
Regards,
Tobias
from po4a.
jonassmedegaard
commented on August 17, 2024
Quoting Dr. Tobias Quathamer (2018-11-04 15:14:19)
Am 03.11.2018 um 18:50 schrieb Jonas Smedegaard:
> Thanks.
>
> Perhaps I was not at the front page when I searched, and that is
> required to locate personal git repos.
>
> Re-pushed my changeset, now linked to yours, and did an MR:
> https://salsa.debian.org/mquinson/po4a/merge_requests/72
Hi,
thanks a lot for this, I've merged it on github. The MR on salsa could
now be closed. Sorry for the inconvenience of not doing this
automatically.
Thanks. And no worries about the lack of aautomation - I choose to
stray off of your chosen development style and accept pain that goes
with that.
- Jonas
…--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
from po4a.
mquinson
commented on August 17, 2024
Hello @toddy15, thanks for taking care of this. Next time, if you prefer, you could simply comment on the pull request saying that it looks good to you, and I'll click for you and resynchronize the repos.
Another possibility, of course, would be that you request an account on salsa to become an official contributor of that project too ;)
Anyway. Thanks again for taking care of this. I just had to push the commits you integrated to salsa to get the MR closed automatically.
from po4a.
toddy15
commented on August 17, 2024
Sorry to have caused more work for you. I am on salsa, BTW, my username is toddy. :-)
from po4a.
mquinson
commented on August 17, 2024
You did not cause more work. To the contrary: you did the review, and I had a git pull + a git push to do. That's perfect, thanks.
You're added to salsa now.
from po4a.
Related Issues (20)
- Asciidoc / Only first line of a multiline attributes is recognized as assignment HOT 7
- Asciidoc / Keeping original formating HOT 15
- Please provide a bash completion file for the po4a script HOT 4
- [feature] vim help format HOT 4
- zh_CN or zh_CHS? (zh_TW or zh_Hant) HOT 2
- Translations are created both in the path of destdir option in the po4a config and in the current directory HOT 2
- \input should not be parsed when it's part of a verbatim environment (po4a::tex: Cannot find 'main.tex' with kpsewhich)
- Use of uninitialized values when trying to translate the darktable documentation HOT 5
- Build failure with `gettext 0.22`
- Can po4a handle the Doxygen's Source Files, *.doc? HOT 2
- proposal: use xmlcatalog to find docbook.xsl
- po file generated with an extension ending by a dot at middle line height HOT 2
- Ambiguity in license statement HOT 5
- Temp pot file not created HOT 10
- Yaml module fails to generate array like string HOT 12
- .po file language translation to another language tutorial or howto?
- Feature request for AsciiDoc: Translate tables by line HOT 3
- Creating an empty .po file causes non-ASCII characters to be silently discarded from msgids HOT 6
- Broken parsing of files with Unicode BOM HOT 1
- Asciidoc: Problem with + in list items HOT 8
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from po4a.