2 May
2012
2 May
'12
12:52 a.m.
On Wednesday 02 of May 2012 02:18:12 Timothy Pearson wrote:
Yes, this is correct. I am waiting to do so until I
get an official
sign-off that the new packages work better than the old ones (i.e. users
are reporting that the new packages do not crash, etc.).
I pause tide of updates, so that users can test. :)
Honestly I'm not sure how to do this in anything
resembling a sane manner
in GIT. I was considering distribution of the large patch file as an
update to the existing 3.5.13 sources, but comments and discussion are
definitely welcome on this subject!
With Git I still do not know how much. But I was in CVS can be tagged branch,
in which the patches can grow independently of the main branch. I suppose it
is possible also in the GIT. And so - to separate branch - I thought the
inclusion of patches for 3.5.13.1 (or how to be named).
Tim
Slavek
--