Bug#893083: Hello Vcs fields

2022-11-20 Thread Santiago Vila

I see you have reverted, thanks a lot.

El 20/11/22 a las 20:51, Geert Stappers escribió:

Which way will it be?


The opposite of "forced" would be "voluntary" and "consensual".

I have experience with git and github, but there are a lot of things 
about salsa which I would like to ask somewhere before switching to git.


If you volunteer to mentor me on those issues, please contact me privately.

Just an example of the kind of doubts I have, feel free to ask in this 
bug report if you like:


It would be easy for me to add those vcs fields to the debian/control 
file in the Debian hello package, but I'm not very happy with the 
current repository you created there because it does not have any 
history at all, not even from 2.10-1 (the first debian release based on 
such upstream version).


The simple question is: Would it be acceptable to have a "temporary" git 
repository, add vcs fields to the hello package, and later replace the 
current repository by a better one, possibly forcing everybody to rebase 
to the fixed repository as a result? In other words: It is acceptable to 
change history for the "higher goal" of having a better history?


That's just an example of the kind of things I would like to know before 
being comfortable with a git repository.


Thanks.



Bug#893083: Hello Vcs fields

2022-11-20 Thread Geert Stappers
On Sun, Nov 20, 2022 at 07:48:04PM +0100, Santiago Vila wrote:
> El 20/11/22 a las 18:27, Geert Stappers escribió:
> > tag 893083 + pending
> 
> Please don't.


> While I agree that it would be better to use git,
> forcing it via NMUs is unwelcome.

Which way will it be?


Groeten
Geert Stappers
-- 
Silence is hard to parse


signature.asc
Description: PGP signature