From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?ISO-8859-1?Q?R=FCdiger?= Sonderfeld Newsgroups: gmane.emacs.devel Subject: Re: Git transition checklist Date: Thu, 09 Jan 2014 17:45:28 +0100 Message-ID: <3639960.702bQ2ZvO3@descartes> References: <20140108135200.8ECF9380834@snark.thyrsus.com> <87y52pmmvw.fsf@igel.home> <837ga9dt8v.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1389286910 25798 80.91.229.3 (9 Jan 2014 17:01:50 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 9 Jan 2014 17:01:50 +0000 (UTC) Cc: esr@thyrsus.com, Andreas Schwab , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 09 18:01:55 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1W1IzT-0005Zy-2u for ged-emacs-devel@m.gmane.org; Thu, 09 Jan 2014 18:01:55 +0100 Original-Received: from localhost ([::1]:52929 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W1IkR-00070t-D4 for ged-emacs-devel@m.gmane.org; Thu, 09 Jan 2014 11:46:23 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53768) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W1Ijt-0006cx-2Y for emacs-devel@gnu.org; Thu, 09 Jan 2014 11:45:53 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W1Ijn-0000Sg-9i for emacs-devel@gnu.org; Thu, 09 Jan 2014 11:45:48 -0500 Original-Received: from ptmx.org ([178.63.28.110]:40407) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W1Ijh-0000RA-LQ; Thu, 09 Jan 2014 11:45:37 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by ptmx.org (Postfix) with ESMTP id 226FC24CF4; Thu, 9 Jan 2014 17:45:36 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at ptmx.org Original-Received: from ptmx.org ([127.0.0.1]) by localhost (ptmx.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ixbowMkD+B9B; Thu, 9 Jan 2014 17:45:34 +0100 (CET) Original-Received: from descartes.localnet (chello080108246092.7.14.vie.surfer.at [80.108.246.92]) by ptmx.org (Postfix) with ESMTPSA id 7316E24B89; Thu, 9 Jan 2014 17:45:34 +0100 (CET) User-Agent: KMail/4.11.3 (Linux/3.11.0-14-generic; KDE/4.11.3; x86_64; ; ) In-Reply-To: <837ga9dt8v.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 178.63.28.110 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:167938 Archived-At: On Thursday 09 January 2014 18:17:52 Eli Zaretskii wrote: > > From: Andreas Schwab > > Cc: R=C3=BCdiger Sonderfeld , > >=20 > > esr@thyrsus.com, emacs-devel@gnu.org > >=20 > > Date: Thu, 09 Jan 2014 12:10:27 +0100 > >=20 > > Eli Zaretskii writes: > > > If you suggest doing the above by hand, then that won't do the jo= b: > > > people will forget and/or use different formats for the text. We= need > > > something better, if it's possible. > >=20 > > Notes can be added, removed and modified independently from the com= mits > > they are attached to, so anybody can fix it up. >=20 > Yes, but only after the problem is discovered and/or reported. Until= > then, it could lay dormant for a long time. Again, this happened in > the past. What does --fixes in bzr exactly do? Does it close the corresponding b= ug on=20 the tracker? Does that happen when you commit or when you push? This could be handled automatically in a pre-receive hook. It depends = on what=20 exactly we need to do. Is it enough to check the format? That would b= e=20 simple. Checking if it matches an existing bug and closing the bug wou= ld be a=20 bit more complicated because it requires interaction with the bug track= er. But I'm currently more concerned with the fact that notes aren't automa= tically=20 pushed. So maybe git-notes aren't useful in our case. Regards, R=C3=BCdiger