Follow-up Comment #2, sr #109326 (project administration):
Thank you for your prompt response.
>Since texinfo traditionally used svn, I assume someone (Karl?) added this
hook or asked this hook to be added to protect against undesirable commits.
It still uses svn. We were just going to use git for the GSOC project. The
person doing the project is currently using a git repository hosted on another
site and we thought it would be a good idea to move it to Savannah.
>perhaps it's good to consult with Karl about why was it there in the first
place ?
It was obviously there to prevent people from adding commits which should have
been made to the svn repository instead. If you insist, I can point him to
this discussion, but I don't see why he should have any objections.
The note I was trying to add to the README file was
"NOTE: This Git repository is for Mathieu Lirzin's
Google Summer of Code project in 2017. Do not use it to get the
latest Texinfo sources."
>So I recommend either using a dedicated branch and not committing to 'master'
anything except official 'texinfo' commits.
I think it would be a good idea to use a different branch. The existing branch
'master' can either be left as it is or removed, whatever is easiest.
>We can also create a dedicated sub-repository (something like:
`texinfo/gsoc2017.git`).
>Then it won't interfere with the real repository.
There's probably no advantage to this approach over using a separate branch.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/support/?109326>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
