Re: [Debian PAPT] Question about salsa repo and packaging
On 2018-09-16 at 01:32:05 -0400, Sergio Durigan Junior wrote: > > 1. I'd like to revert some changes to the salsa repo for my package, as > > these changes were never uploaded to Debian and are not superseded by > > new upstream package. Is it OK to do a "git reset --hard " to make > > them disappear in my repository? > > You mean do a "git reset --hard" locally and then "git push" the > modified history? This is not ideal, but if you're the only one using > the repository, and if there was no Debian release containing the code > you're reverting, then I'd say it's OK. can one be sure that nobody else is using the repository? maybe nobody in debian, but what about our derivatives? or even our users if there is a strong need to remove those changes (e.g. for copyright reasons) I agree that a reset --hard is a reasonable option, but if it's just to keep the repo clean my personal preference would be for a ``git revert`` that doesn't break the repo for other users. -- Elena ``of Valhalla'' signature.asc Description: PGP signature
I'll be offline for an indefinite period
Hello, I will be offline for an indefinite period. I maintain those packages in python team: wikitrans, pyfribidi, okasha, and python-uinput. -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7 GPG Fingerprints: 6E2E E4BB 72E2 F417 D066 6ABF 7B30 B496 A7EF 5761 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7 signature.asc Description: PGP signature
Re: [Debian PAPT] Question about salsa repo and packaging
On Sunday, September 16 2018, Elena wrote: > On 2018-09-16 at 01:32:05 -0400, Sergio Durigan Junior wrote: >> > 1. I'd like to revert some changes to the salsa repo for my package, as >> > these changes were never uploaded to Debian and are not superseded by >> > new upstream package. Is it OK to do a "git reset --hard " to make >> > them disappear in my repository? >> >> You mean do a "git reset --hard" locally and then "git push" the >> modified history? This is not ideal, but if you're the only one using >> the repository, and if there was no Debian release containing the code >> you're reverting, then I'd say it's OK. > > can one be sure that nobody else is using the repository? maybe nobody > in debian, but what about our derivatives? or even our users > > if there is a strong need to remove those changes (e.g. for copyright > reasons) I agree that a reset --hard is a reasonable option, but if it's > just to keep the repo clean my personal preference would be for a ``git > revert`` that doesn't break the repo for other users. I understand and agree with your comment, but it seems like his commits are pretty recent. As I said, overwitting history is never ideal, but under specific circumstances I think it's "ok-ish". But sure, if you're comfortable with using "git revert", then by all means, go ahead. -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/ signature.asc Description: PGP signature
Re: I'll be offline for an indefinite period
On Sunday, 16 September 2018 10:29:23 PM AEST أحمد المحمودي wrote: > I will be offline for an indefinite period. I hope you are all right, or will be all right. Take care and good luck. -- Regards, Dmitry Smirnov. --- To predict the behavior of ordinary people in advance, you only have to assume that they will always try to escape a disagreeable situation with the smallest possible expenditure of intelligence. -- Friedrich Nietzsche signature.asc Description: This is a digitally signed message part.
