Correct names and email addresses in Git history about at HOT 9 CLOSED

@carmignani @lnadolski @bnash @simoneliuzzo @gioAlea @yrtan @lfarv could you please confirm the name and email address you would like to be stored in Git history?

We also have contributions from peacechang, xiahuang and thperron2001. Can we contact them?

This should also be configured for Git as described here: https://git-scm.com/book/en/v2/Getting-Started-First-Time-Git-Setup so that future commits match up too.

from at.

I don't like the idea of rewriting the history: the addresses are as they were when the commit was done, and it makes sense. I don't think you'll rewrite the whole history every time someone changes his mail address !
Now everybody has to move to git, so he will put in his config the most recent address, and all new commits will be up-to-date.
You also cannot ask everybody to reclone all the repositories. Though it is not what the instructions say (fetching is easier than cloning again):

"any person with forks or clones must fetch the rewritten history..."

So please let the history as it is, we know all those people...

from at.

@lfarv, we had a short email exchange about this. I understand the point is to make a correction on an error in Nicola's email (.rf instead of .fr) and also to correct any other emails during this transition between sourceforge to github, so that everyone's contributions shows up here
https://github.com/atcollab/at/graphs/contributors
It would be a one time change as a part of the transition from Sourceforge to GitHub. We could send an email to the mailing list to tell people what to do.

I don't know if Peace, Xiaobiao or Thomas have github accounts. The email addresses I have for them are Peace: [email protected], Xiaobiao: [email protected] and Thomas: [email protected]

For myself, the esrf.fr email won't last much longer, so I prefer the gmail.com address.

from at.

In general it is not advisable to change Git history. You can fetch the changed repository but the old master branch and the new one will be different, so the easiest way to manage it is to re-clone. Anyone who has a branch in progress has to be careful.

The problem is that I had to provide the email addresses at the time of converting from Subversion, and I made a mistake in Nicola's and provided dummy addresses for everyone I didn't know of.

We would do this once only. In any case, I do not really have an opinion and I am happy with what the agreed consensus is.

from at.

I am still not convinced of the necessity to rewrite Git history. There are ~ 8 clones here at ESRF, some used for the machine operation, and I do not feel comfortable saying to some people (not git experts !) that they have to start again from zero. I have also here several local branches open… We moved away from SourceForge hoping to have something more stable, so please keep it such. Anything you do should be transparent for users.

Concerning the wrong email adresses, I don't see the problem: every user can easily update his profile on the Github site. These adresses will frequently change: Boaz's now, mine in ~2 months… Only the most recent address is relevant, addresses associated with old Subversion commits don't really matter.

So I strongly insist on keeping the repository stable: it's too late, the switch to Github has already occurred, at least at ESRF

from at.

from at.

Newbie to git. My profile does have my correct email. As for history, as long as the git username is valid that should be enough for people to contact the person that made the change if necessary.

from at.

At the moment, I'm not actively developing with this repository, so it doesn't bother me to make the change. But if those who are using this repository are not comfortable with it, then I can agree not to.

from at.

I apologise to Nicola, but I think it has been agreed that this is no longer possible.

from at.