From: Ergus via "Emacs development discussions." <emacs-devel@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, johanclaesson@bredband.net,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: master b82adee: Invalidate dir-locals-directory-cache when writing dir-local file
Date: Mon, 19 Aug 2019 18:45:04 +0200 [thread overview]
Message-ID: <20190819164504.sgszy627z3rmqjxi@Ergus> (raw)
In-Reply-To: <831rxhmcvc.fsf@gnu.org>
On Mon, Aug 19, 2019 at 05:46:47PM +0300, Eli Zaretskii wrote:
>> From: Stefan Monnier <monnier@iro.umontreal.ca>
>> Cc: Lars Ingebrigtsen <larsi@gnus.org>, johanclaesson@bredband.net, emacs-devel@gnu.org
>> Date: Mon, 19 Aug 2019 05:32:20 -0400
>>
>> >> Oops; forgot the "Copyright-paperwork-exempt: yes", and I guess it's too
>> >> late to amend after I've pushed?
>> > Too late.
>>
>> Yup. Hard to believe we're still stuck with this problem of "unfixable
>> commit messages" after all these years.
>
>We can solve it easily if we go back to CVS.
>
This can be fixed with a rebase or a note.
But
A rebase in a public repo is not recommended, so that's why the
fork-join workflow is usually more extended (and the default in gitlab,
github and bitbucked). So the user pushes, rebases and fixes in it's
fork freely as in a local branch, with the advantage that other users
can pull/test and comment the changes (code, message, number of commits,
benchmarks, tests) before they go in the main repo. And only few users
have write access to the master repo and they decide how to add the
changes with a rebase, a merge or a rebase+merge with no-ff (to have
linear or grouped history...).
next prev parent reply other threads:[~2019-08-19 16:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190818224934.1914.38804@vcs0.savannah.gnu.org>
[not found] ` <20190818224935.1ACDA20A0E@vcs0.savannah.gnu.org>
2019-08-18 22:51 ` master b82adee: Invalidate dir-locals-directory-cache when writing dir-local file Lars Ingebrigtsen
2019-08-19 2:37 ` Eli Zaretskii
2019-08-19 9:32 ` Stefan Monnier
2019-08-19 9:52 ` Štěpán Němec
2019-08-19 17:05 ` Noam Postavsky
2019-08-20 7:48 ` Štěpán Němec
2019-08-19 14:46 ` Eli Zaretskii
2019-08-19 16:45 ` Ergus via Emacs development discussions. [this message]
2019-08-19 17:25 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190819164504.sgszy627z3rmqjxi@Ergus \
--to=emacs-devel@gnu.org \
--cc=eliz@gnu.org \
--cc=johanclaesson@bredband.net \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=spacibba@aol.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).