I would strongly *PREFER* someone look at it before entering it into the
Even several someones.
What we pushed yesterday for the buffer-colors and icon-themes is code
for months, on two machines, which hardly represents all configurations
out there by
I was unhappy about pushing the icon-themes without the extra themes.
It really doesn't
show what it does without a few themes to try it out on. I really need
to get a Bitbucket
repository this morning for extra icon themes, and get it uploaded so
reviewers can use the
extra icons to actually see what it does. The two default themes in the
text-icons and default icons, each of which has only 1 size, isn't
enough to put it through
it's paces. Might even have errors that way too.
One question: will one of you give us the go ahead to push the changes?
Or do we wait
for a week(or 2) with no requests for us to change things to push it? I
expect us to make
mistakes--this is the first time we are doing most of the package stuff.
Today is Byrel's last day home before going back to grad school. We can
do bug fixes, etc
in the meantime, but large sections of code probably will have to wait
We will get a bitbucket repository for the icon-themes-list with the 3
themes and Icons
in it, up this morning.
steven Mitchell <smitchel(a)bnin.net> writes:and integrating icon-themes
I think the path we want to encourage is that you create a
under your own Bitbucket account, and let one of use have one last look
at it before cloning it over to the XEmacs account. Does that work for
Happy to cooperate, just please show us the way things need to be done.
Is this path for new packages only? Or does it include improvements to
packages as well, and diffs to documentation, and website stuff? I am
about the update to xpm-mode that we pushed a couple of weeks ago, should we
have put that in a repository first?
XEmacs-Beta mailing list