From: Karl Fogel <kfogel@red-bean.com>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org, Stefan Monnier <monnier@IRO.UMontreal.CA>,
Sven Joachim <svenjoac@gmx.de>
Subject: Re: No commit messages on emacs-diffs after the switch to bzr
Date: Tue, 05 Jan 2010 22:41:19 -0500 [thread overview]
Message-ID: <87637fnbmo.fsf@red-bean.com> (raw)
In-Reply-To: <oiwrzw0ycx.fsf@fencepost.gnu.org> (Glenn Morris's message of "Tue, 05 Jan 2010 21:18:54 -0500")
Glenn Morris <rgm@gnu.org> writes:
>Karl Fogel wrote:
>> https://savannah.gnu.org/support/index.php?107190
>
>I hope this can be fixed soon, I consider this an important feature.
>(I see the ticket is indeed classed as "important".)
>
>Anyone know if there is any chance of getting the backlog of missing
>diffs when it is fixed?
>
>BTW, you wrote "emacs-commit at gnu.org" in the ticket, but it is
>"emacs-diffs" (as in the subject of this topic):
>
>http://lists.gnu.org/mailman/listinfo/emacs-diffs
Thanks. I went and checked in my mail folders to see, but of course,
the commits used to be split across two different list (one for metadata
about the change, the other for the diffs themselves), and I must have
grabbed the address of the former.
I've updated the ticket now.
>Also, some parts of Emacs (mh-e and possibly org and others) had
>previously asked Savannah for special rules to get duplicates of
>relevant commit messages to their own mailing lists; I imagine they'll
>want to keep those rules.
Also added this question to the ticket.
-Karl
prev parent reply other threads:[~2010-01-06 3:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 11:24 No commit messages on emacs-diffs after the switch to bzr Sven Joachim
2009-12-28 15:33 ` Karl Fogel
2009-12-29 18:24 ` Stefan Monnier
2010-01-02 19:33 ` Karl Fogel
2010-01-06 2:18 ` Glenn Morris
2010-01-06 3:41 ` Karl Fogel [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87637fnbmo.fsf@red-bean.com \
--to=kfogel@red-bean.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=rgm@gnu.org \
--cc=svenjoac@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.