Op 25-2-2020 om 10:08 schreef Andrea Pescetti:
On 24/02/2020 Dick Groskamp wrote:
OK, I think I messed up big time.
I think I made the changes on Apache/OpenOffice, not in
DiGro/OpenOffice.
Is it possible to safely remove my PR's ?
No that is not the issue. It is supposed to be that way. The way PRs
work is this one:
- You create what Github calls a "fork" (your personal copy)
- You commit and push stuff to your fork, usually in a dedicated branch
- When everything is ready, you submit your commits (all of them and
not each of them separately, like you did) as a PR for the "upstream"
repository, i.e., apache/openoffice
Or should I close them all.
No, please don't. If I find some time to explain in practice how to do
it, I'll combine your PRs and explain, so that everyone doing this in
the future can have a reference.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: l10n-unsubscr...@openoffice.apache.org
For additional commands, e-mail: l10n-h...@openoffice.apache.org
Andrea,
I found the way to do it.
However, my latest PR, called LATEST, contains 3 files that shouldn't be
there.
Two are about .gitattributes (I added the file but later forgot about it
and encountered it after I made the PR. Then deleted the file, which is
the second .gitattribute commit.)
Last commit concerns a resolved conflict.
Therefore only the commits with "Removed whitespace" should be pushed to
trunk.
Don't know if that is possible though.
--
DiGro
___________________________
Apache OpenOffice 4.1.7 (Dutch) and scanned with Ziggo Safe Online (F-Secure)
---------------------------------------------------------------------
To unsubscribe, e-mail: l10n-unsubscr...@openoffice.apache.org
For additional commands, e-mail: l10n-h...@openoffice.apache.org
