From: Bastien <bzg@altern.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Michael Albinus <michael.albinus@gmx.de>,
Stefan Monnier <monnier@IRO.UMontreal.CA>,
emacs-devel@gnu.org
Subject: Re: ChangeLogs in the elpa branch
Date: Tue, 27 Sep 2011 11:04:58 +0200 [thread overview]
Message-ID: <87pqimjqyt.fsf@gnu.org> (raw)
In-Reply-To: <m3ty7yz7kd.fsf@hase.home> (Andreas Schwab's message of "Tue, 27 Sep 2011 10:57:22 +0200")
Andreas Schwab <schwab@linux-m68k.org> writes:
> The principle is actually: "Don't modify published history." It is
> perfectly ok to edit commits locally until you are happy with them
> before publishing them.
You're perfectly right, thanks for the precision.
--
Bastien
next prev parent reply other threads:[~2011-09-27 9:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 7:09 ChangeLogs in the elpa branch Michael Albinus
2011-09-26 9:56 ` Julien Danjou
2011-09-26 10:23 ` Lars Magne Ingebrigtsen
2011-09-26 10:35 ` Michael Albinus
2011-09-26 14:23 ` Ted Zlatanov
2011-09-26 15:52 ` Stefan Monnier
2011-09-26 16:49 ` Ted Zlatanov
2011-09-26 21:13 ` Richard Stallman
2011-09-26 11:46 ` Dave Abrahams
2011-09-26 13:03 ` Stefan Monnier
2011-09-26 13:49 ` Michael Albinus
2011-09-26 16:26 ` Glenn Morris
2011-09-26 16:38 ` Lars Magne Ingebrigtsen
2011-09-26 19:18 ` Andreas Schwab
2011-09-26 17:06 ` Eli Zaretskii
2011-09-26 17:08 ` Stefan Monnier
2011-09-26 21:18 ` Michael Albinus
2011-09-26 21:27 ` Lars Magne Ingebrigtsen
2011-09-27 3:10 ` Michael Albinus
2011-09-27 5:22 ` Bastien
2011-09-27 8:57 ` Andreas Schwab
2011-09-27 9:04 ` Bastien [this message]
2011-09-27 9:25 ` Eli Zaretskii
2011-09-27 13:00 ` Stefan Monnier
2011-09-27 7:10 ` Glenn Morris
2011-09-27 9:05 ` Juanma Barranquero
2011-09-27 9:45 ` joakim
2011-09-27 12:02 ` Stephen J. Turnbull
2011-09-27 13:05 ` Stefan Monnier
2011-09-27 9:00 ` Juanma Barranquero
2011-09-27 12:24 ` Thien-Thi Nguyen
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=87pqimjqyt.fsf@gnu.org \
--to=bzg@altern.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=monnier@IRO.UMontreal.CA \
--cc=schwab@linux-m68k.org \
/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.