2:08 a.m.
According to https://bitbucket.org/xemacs/xemacs-packages, the top-level
repo has not been updated to reflect my push to the gnus sub-repo. Is
this a glitch, or am I misunderstanding the workflow?
mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
5:29 a.m.
Mike Kupfer writes:
According to https://bitbucket.org/xemacs/xemacs-packages, the
top-level
repo has not been updated to reflect my push to the gnus sub-repo. Is
this a glitch, or am I misunderstanding the workflow?
Somebody needs to explicitly commit and push at top-level. I forget
whether we decided that only Norman is allowed to, or if the developer
who did the original commit should do it.
Steve
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
5:56 a.m.
Stephen J. Turnbull wrote:
Somebody needs to explicitly commit and push at top-level. I forget
whether we decided that only Norman is allowed to, or if the developer
who did the original commit should do it.
I think we decided that only Norbert touches the top-level stuff. What
I'm hazy on is whether the top-level commit/push should be done as a
matter of course when the new package tarball is published, or if the
package maintainer is supposed to email Norbert to ask him to do it. (I
think the former makes more sense.)
mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
7:41 a.m.
Mike Kupfer writes:
What I'm hazy on is whether the top-level commit/push should be
done as a matter of course when the new package tarball is
published,
Ah. That depends on how obvious it is to Norbert that somebody has
messed with the tree. ;-) With git submodules, IIRC you need to use a
separate command to even get information that a submodule has changed
("git status" won't tell you, I think).
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
10:57 p.m.
>>>> Mike Kupfer <mike.kupfer(a)xemacs.org> writes:
I think we decided that only Norbert touches the top-level stuff.
That's how I got it too.
What I'm hazy on is whether the top-level commit/push should be
done
as a matter of course when the new package tarball is published, or
if the package maintainer is supposed to email Norbert to ask him to
do it. (I think the former makes more sense.)
I think the process is that you mail Norbert when you have committed a
package. He then updates the package Makefile and ChangeLog and
commits that and then finally commits on the top level the package
together with possibly other packages that are ready.
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
7:55 p.m.
Mats Lidell wrote:
>>>>> Mike Kupfer <mike.kupfer(a)xemacs.org>
writes:
> What I'm hazy on is whether the top-level commit/push should be done
> as a matter of course when the new package tarball is published, or
> if the package maintainer is supposed to email Norbert to ask him to
> do it. (I think the former makes more sense.)
I think the process is that you mail Norbert when you have committed a
package. He then updates the package Makefile and ChangeLog and
commits that and then finally commits on the top level the package
together with possibly other packages that are ready.
What I find confusing is that a new package tarball has been built and
posted for download. So presumably Norbert already knows that I pushed
something. I had expected that the commit and push to the top-level
repo in Bitbucket would happen as part of that publication process.
If there's value in separating those two things (publishing the new
tarball and updating the top-level repo), I can certainly live with
sending a separate request to update the top-level repo. But at the
moment I don't see any value in having them separate operations.
cheers,
mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
4:52 p.m.
>>>> Mike Kupfer <mike.kupfer(a)xemacs.org> writes:
What I find confusing is that a new package tarball has been built
and posted for download. So presumably Norbert already knows that I
pushed something.
Hmm.. It seems so. Norbert can hopefully explain this.
Yours
--
%% Mats
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
4497
days inactive
4502
days old
6 comments
3 participants
participants (3)
-
Mike Kupfer -
Stephen J. Turnbull -
The XEmacs Package Smoketest