On 19.12.2014 16:38, Fernando de Oliveira wrote:
On 19-12-2014 12:11, Armin K. wrote:
On 19.12.2014 10:40, Fernando de Oliveira wrote:
I have updated my local copy of the repository:
$ svn update
Updating '.':
A trunk/MesaLib/MesaLib-10.4.0-add_xdemos-1.patch
Atualizado para revisão 3077. [Updated to revision 3077.]
However, there is no mail corresponding to it.
Please, who did the update?
Me.
Thanks. i understand that you needed to bump the patch version, is it
true? There was a message everyday about that patch missing.
Yes. But instead of just bumping the version, I took the liberty of
adding newer versions of the files it installs from upstream (I do that
from time to time, last time it was in August I believe).
I refreshed the files from upstream repository. We have patch
headers for exactly these kinds of situations.
I don't understand what you wrote.
It means that I fetched latest version of *.c and *.h files that the
patch adds from their git repository and added them. The patch was
simply too big to appear on the mailing list (over 100 KB, mailman
allows 100 KB). You can use diff against the newer patch and a 10.3.5
one to see what got changed.
It means that anyone of us can modify upstream repository without a
message sent.
I would like to understand why you used this procedure instead of the
usual "bump version".
Also, I don't understand what you mean by "these kinds of situations".
The kinds of situations where commit message doesn't appear on mailing
list. That way, you can see who added it and when (more or less).
Finally, I would like to learn how one can refresh "the files from
upstream repository" the way you did.
Just clone the repository and copy the latest version of the files we
ship as a patch into the mesasrc/xdemos and create a new patch.
--
http://lists.linuxfromscratch.org/listinfo/patches
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
